bug-fix-rhythm

Orchestrates batch-end verification rhythm for multi-fix sessions with parallel tool calls.

5|9|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ajenchen/design-system --skill bug-fix-rhythm-ajenchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix-rhythm
Source: https://github.com/ajenchen/design-system/tree/main/.agents/skills/bug-fix-rhythm
Command: npx skills add https://github.com/ajenchen/design-system --skill bug-fix-rhythm-ajenchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a session contains two or more fixes or a user lists numbered rules, running a full verify cycle after every single fix wastes time and risks silently dropping one of the user's requirements. This Skill enforces a batch-end-verify rhythm so all fixes are completed in parallel batches and verified once at the end against a verbatim MUST-ALL checklist. ## Core Features & Use Cases - MUST-ALL Checklist Extraction: Converts user-listed numbered rules ("rule 1... rule N", Q1-QN, image annotations) into a verbatim checklist where every item must be verified, never ranked or dropped. - Parallel Tool Batching: Groups independent Read/Grep/Glob calls into a single message and batches Edit operations, deferring tsc, audit, and visual verification to one final pass. - Surgical vs Substantive Triage: Classifies each fix as surgical (auto-ship), P2E engineering (autonomous with evidence), or P2H product/UX (stop and propose) before landing changes. - Use Case: A user reports five visual bugs with numbered screenshots. The Skill builds a five-item checklist, applies all edits in one batch, then runs tsc, invariant tests, and pixel-quantified visual audit once, reporting a per-rule verify trace. ## Quick Start Invoke this skill when I list multiple numbered bugs or rules and batch all fixes with a single end-of-session verification report.

Frequently Asked Questions about bug-fix-rhythm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle multiple bug fixes in one AI coding session?

Batch all fixes together instead of verifying each one individually. Extract a MUST-ALL checklist from the user's numbered rules, apply edits in parallel batches, then run type checks, invariant tests, and visual audits once at the end with a per-rule verify report.

When should I use batch-end verification instead of per-fix verification?

Use batch-end verification when a session has two or more fixes or the user lists numbered rules. Skip it for single surgical fixes, pure refactors, typo fixes, or docs-only changes, where a simple per-fix verify is sufficient.

What is a MUST-ALL checklist in multi-fix workflows?

A MUST-ALL checklist captures each user-listed rule verbatim with its target fix, treating every item as mandatory. It forbids ranking rules by priority, paraphrasing user wording, or reporting completion while any item lacks a verification trace.

How does this skill decide which fixes need user approval?

Each fix is triaged as surgical (pixel or token adjustments, auto-shipped), P2E engineering substantive (completed autonomously with evidence and gates), or P2H product/UX substantive (stopped for an explicit user decision). P2H items cannot be smuggled into an engineering batch.

What happens if a fix cannot be verified at runtime?

The skill forbids claiming verification without a trace. Any unverifiable rule must be explicitly flagged as unverified with a note that the user needs to confirm it on a real device, rather than inferred from code reading.