quality-gates

This skill should be used when the user wants to run code quality checks (linting, formatting, type checking, tests) on the lazyopencode project. Use this skill when asked to "run quality gates", "check the code", "run tests", "lint the code", or verify code quality before committing.

$ Instalar

git clone https://github.com/NikiforovAll/LazyOpenCode /tmp/LazyOpenCode && cp -r /tmp/LazyOpenCode/.opencode/skill/quality-gates ~/.claude/skills/LazyOpenCode

// tip: Run this command in your terminal to install the skill


name: quality-gates description: This skill should be used when the user wants to run code quality checks (linting, formatting, type checking, tests) on the lazyopencode project. Use this skill when asked to "run quality gates", "check the code", "run tests", "lint the code", or verify code quality before committing.

Quality Gates

Run code quality checks for the lazyopencode project. This skill executes the same checks used in pre-commit hooks plus tests.

Quality Checks

The following checks are run in order:

CheckCommandPurpose
Ruff Lintuv run ruff check src tests --fixLint code and auto-fix issues
Ruff Formatuv run ruff format src testsFormat code consistently
Mypyuv run mypy srcStatic type checking
Pytestuv run pytest tests/ -qRun test suite

Usage

To run all quality gates:

scripts/check_quality.sh

Or run individual checks as needed using the commands above.

Workflow

  1. Run the scripts/check_quality.sh script from the project root
  2. Review any failures and fix issues
  3. Re-run until all checks pass
  4. Present user with concise summary of results in markdown table format

Common Issues

  • Ruff lint failures: Usually auto-fixed. If not, check the error message for manual fixes needed.
  • Mypy errors: Type annotation issues. Add or fix type hints as indicated.
  • Test failures: Review test output, fix failing tests or underlying code.