Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
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']."
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
中文简介正在准备中。当前显示原文说明。
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
中文简介正在准备中。当前显示原文说明。
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
中文简介正在准备中。当前显示原文说明。
Create a git branch named after a GitHub issue.
中文简介正在准备中。当前显示原文说明。
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
中文简介正在准备中。当前显示原文说明。
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
中文简介正在准备中。当前显示原文说明。