メニュー
Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
| title | code-quality-gate |
| name | code-quality-gate |
| description | Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality. |
| disable-model-invocation | true |
| allowed-tools | Bash(gh pr *) |
Run the complete code quality gate for this PR.
Check whether an open PR exists:
!gh pr view --json number,title,headRefName 2>/dev/null || echo "NO_PR"
If the output above contains "NO_PR", note that no PR is open. Proceed with the scans anyway, but print the final report to the terminal instead of posting it as a comment.
Run /security-scan. It will return findings in this format:
SECURITY FINDINGS:
- [severity] file:line — description
Capture the full output.
Run /complexity-check. It will return findings in this format:
COMPLEXITY FINDINGS:
- file:line — description
Capture the full output.
Run /test-coverage-check. It will return findings in this format:
COVERAGE FINDINGS:
- source-file — description
Capture the full output.
Collect all three findings blocks.
If a PR is open, invoke @quality-reporter with this message:
"Post a code quality report for this PR with the following findings. Format as a GitHub PR comment and post it.
[paste the SECURITY FINDINGS block here]
[paste the COMPLEXITY FINDINGS block here]
[paste the COVERAGE FINDINGS block here]"
Confirm the comment URL was returned and print it.
If no PR is open, format and print the report to the terminal using the same structure the quality-reporter would use.
After posting (or printing), output a summary: "Code quality gate complete. Security: [count or 'clean'], Complexity: [count or 'clean'], Coverage: [count or 'clean']."