القائمة
Shared quality gates all phases must pass before proceeding. Single source of truth for pre-commit, tests, code quality, security, performance, documentation, CI, and acceptance criteria.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | quality-gates |
| description | Shared quality gates all phases must pass before proceeding. Single source of truth for pre-commit, tests, code quality, security, performance, documentation, CI, and acceptance criteria. |
| user-invocable | false |
Single source of truth for quality gates across all phases. Each phase links here instead of restating.
pre-commit run --all-files
Must pass: formatting (black/prettier/gofmt), linting (ruff/eslint/golangci-lint), type checking (mypy/tsc), import sorting, trailing whitespace, large-file detection.
Unit: every new/modified function tested; happy path + edge cases + errors; deterministic; <5s for full unit suite.
Integration: main workflows covered; external dependencies mocked appropriately.
Coverage: meets or exceeds target (usually 80%+); no decrease from baseline.
gosec / npm audit / bandit)All automated checks pass: build · unit tests · integration tests · linting · type checking · security · performance · coverage threshold.
# Python
pre-commit run --all-files && pytest && ruff check . && mypy src/
# Go
pre-commit run --all-files && go test ./... && golangci-lint run
# Node/TypeScript
pre-commit run --all-files && npm test && npm run lint && tsc --noEmit
Before proceeding to the next phase, ALL of the above must be green.
Periodic, repo-agnostic doctor for AI-context files (CLAUDE.md, AGENTS.md, .cursorrules, .github/copilot-instructions.md). Verifies every concrete claim against the current repo, lints against an opinionated quality spec, surfaces newly-added subsystems the doc misses, and proposes the minimum edits to restore health. Conservative pruning. No-op when files are already healthy — safe to run on a cron.
Refine GitHub issues by creating WHAT/WHY/HOW sections and preparing them for implementation. Adds issues to GitHub Projects V2, sets status to "Ready", and assigns the current iteration.
Transform a GitHub issue into a production-ready pull request with automated PR review. Executes full workflow including refinement check, code generation, RL loop, testing, PR creation, automated review, feedback application, and re-verification before marking ready for human review.
Shared skill for GitHub Projects V2 API operations. Includes GraphQL mutations for adding issues, updating status, and managing iterations.
Transform ambiguous GitHub issues into refined specifications with WHAT, WHY, and HOW sections. Use before implementing features or fixes when issue lacks clear requirements.
Generate production-quality code following acceptance criteria from refined issue, with comprehensive tests and documentation. Use after issue refinement (Phase 1) is complete.