align-grid
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a…
Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.
$ npx -y skills add danielvm-git/bigpowers --skill respond-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/respond-reviewContext preview
The summary Claude sees to decide when to auto-load this skill.
Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.
name: respond-review model: sonnet effort: standard description: Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.
> **HARD GATE** — **HARD GATE** — Every reviewer comment must be addressed (fix, disagree + document reason, or ask clarification). Do NOT ignore feedback and merge.
Work through reviewer findings systematically. Don't apply changes blindly — categorize first, then decide, then fix, then verify.
Read every finding before acting on any of them. Get the full picture first.
For each finding, assign a category:
| Category | Meaning | Action | |----------|---------|--------| | **must-fix** | Correctness bug, security issue, test failure, CONVENTIONS.md violation | Fix before proceeding | | **should-fix** | Code quality issue, naming, clarity — worth fixing but not blocking | Fix if time allows | | **consider** | Architectural suggestion, alternative approach — may or may not apply | Discuss with user |
Create a numbered list of all findings with their categories.
For each "consider" item, briefly describe the trade-off and ask: "Apply, skip, or discuss?"
Fix every must-fix item. For each one:
Apply should-fix items. If any are large enough to warrant their own commit, note them separately.
After all changes are applied:
<full test command> <typecheck command> <lint command>
Summarize what was applied and what was skipped:
Applied (must-fix): #1, #2, #3 Applied (should-fix): #4 Skipped (consider): #5 — agreed with user to defer All tests pass.
Suggest next skill: `commit-message`.
Agent skills synthesizing 17 years of software engineering discipline — from Clean Code to AI-native architecture — into a single, prescriptive methodology for solo developers.
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a…
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage.…
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout…
Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY…
Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or…
Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and…