Skip to content
cccskills
FreePublished on GitHub

commit-review

[Code Quality] Review an exact pending commit when the commit skill selects lightweight review or the user requests it. --fix-loop repairs and re-reviews; no Git publication authority.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.9 KB
  • references/fix-loop.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

  1. Resolve the intended commit and its purpose; load applicable project review rules and overlays. In --fix-loop, read references/fix-loop.md and snapshot the exact candidate before review; preserve unrelated work.
  2. Inspect every changed file and affected callers for correctness, regressions, security and unnecessary complexity. Trace changed behavior through success, failure and boundary cases; check permissions and affected callers where relevant. Check changed behavior against its configured canonical owner/spec, profile-declared scenario/case and executing test evidence; read further references only for an actual concern. For changed behavior, identify a realistic bug the test should catch; use a targeted mutation probe only when test strength is unclear and edits are authorized.
  3. Validate concerns inline against source and counterevidence. Findings need a reachable trigger, consequence, file:line, severity and ≥85% confidence; omit speculative advice, unrelated debt and issues already caught by checks. Missing required evidence blocks a pass.
  4. Default to read-only. With --fix-loop, fix validated issues within scope and freshly review the whole updated candidate, at most two rounds; --loop-owner=caller stays read-only. Stop with unresolved MEDIUM+ or failed checks; defer nonblocking LOWs. Never extend the budget silently.
  5. Report findings, fixes, checks, rounds and deferred LOWs briefly. Issue a receipt only after a fully covered fresh fix-loop pass and passing required checks, using its original snapshot. Never stage, commit or push from this review; do not load another review workflow routinely.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Code Quality] Use when a workflow step or the user asks for AI code or plan review: LLM calls, prompts, agents, RAG, evals and guardrails. --mode={code|plan}; --report-only is read-only.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Architecture] Use when a workflow step or the user asks for architecture design, compliance review, scalability grading or whole-project audit via --mode={design|review|scalability|full}.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Content] Use when a workflow step or the user asks for business viability: Business Model Canvas, financials, risks and go-to-market recommendation.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Code Quality] Use when a workflow step or the user asks for a focused code-change review: staged, unstaged, branch diff or simple pull request. --fix-loop fixes and re-reviews. Complex pull request: workflow-review-changes; rationale: why-review.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

See all skills by duc01226

Report a problem with this skill