changes-review
[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…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-17 00:07
41,343 results
[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…
[Code Quality] Use when evaluating received review feedback, reviewing named code on request, or verifying a completion claim. Current diffs: changes-review;…
[Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.
[Architecture] Use when a workflow step or the user asks for DDD domain modeling: contexts, aggregates, entities, ERD and events. --mode=review checks entity…
[Implementation] Use when the user asks to build a feature from an idea or description with no plan file yet: research and trace the code, create and get the…
[Implementation] Use when a workflow step or the user asks for root-cause fixes with regression coverage. --target={ci|issue|logs|review|test|types|ui} scopes…
[Git] Use when generating developer KPI, contribution, effort point, man-day or code-quality reports from git history.
[Code Intelligence] Use when building/syncing the code graph, querying callers/imports/tests, tracing flow, checking blast radius, linking APIs or exporting…
[Fix & Debug] Use when a workflow step or the user asks for read-only code-flow investigation. --mode=debug finds bug root causes; --mode=explain narrates…
[Code Quality] Use when analyzing npm package upgrades, outdated dependencies or breaking changes and preparing a phased upgrade plan.
[Debugging] Use when a workflow step or the user asks for performance bottleneck analysis and validated fixes: queries, memory, network, rendering and…
[Planning] Use when a workflow step or the user asks for implementation planning. --mode=review supports review-only or --fix-loop; validate interviews,…
[Code Quality] Use when asked for a final or full review of a pull request or branch, or to check a branch before marking its PR Ready. Reviews the whole…
[Utilities] Use when setting up or re-evaluating portable project context end to end: project-config, reference docs, CLAUDE.md, AGENTS.md. One piece only:…
[Git] Use when asked to create, open, finish, update or mark ready a pull request. Runs in the main session with risk-based test/review choices and automatic…
[Architecture] Use when a workflow step or the user asks for project architecture foundations, infrastructure and examples before feature implementation.
[Documentation] Use when a workflow step or the user asks for one project-reference doc rebuild via --target=<key>, preserving verified rules. All selected…
[Documentation] Use when detecting codebase health issues: unused exports, doc count-drift, orphan files, stale config references.
[Planning] Use when a workflow step or the user asks for adversarial scenarios for failure, data integrity, access, replay and recovery risks before planning.
[Skill Management] Use when creating a skill, adding skill references or scripts, fixing invalid skill headers, or packaging skills.
[Codex] Use once, after the `.claude/**` edits of a change are final and before committing them, to regenerate and verify `.agents/`, `.codex/`, `.opencode/`…
[opencode] Use when running the opencode sync and verify pipeline: opencode.json reconcile, skill policy, per-skill commands, hooks bridge, sub-agent mirror,…
[Documentation] Use when generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. Generator only, never authors business…
[Process] Use when a developer needs to understand and judge scoped work: a change set, subsystem, decision, plan or concept — flow, rationale, trade-offs,…