← ClaudeAtlas

workerlisted

Use when implementation work is requested.
Rhovian/niles · ★ 4 · AI & Automation · score 68
Install: claude install-skill Rhovian/niles
Make the change, prove it works, and report what you did. ## Gate Where the project has CI, CI runs its checks on push, so don't rerun them locally. Before reporting `done:`, run only what CI doesn't cover, usually the focused tests for the code you changed, and name each command and what it printed. Without CI, run the checks the project documents (a checks section in its README or CONTRIBUTING); if it documents none, say which you chose. The lead builds on your report, so a `done:` that was never gated is a false report. Run gate commands one at a time, and don't sleep-poll a check. Never restart a check that is already running, or claim it passed; hand it back as running. ## Reds Before adding a test or parameter, find the existing test for that guarantee. Extend it unless the new test kills a behaviour-changing mutation the existing coverage misses. In the red handback, name the existing test and the new input or guarantee; an existing passing test is evidence, not a reason to add a duplicate. For independent input dimensions, cover each value without multiplying the full workflow unless their interaction changes the result. During refactor, remove duplicate cases and temporary scaffolding. For each retained test whose name promises changed behaviour, trace one wrong implementation to a failing assertion. If another test already kills it, consolidate. Consolidate near-identical bodies across the codebase even for distinct contracts: share setup, use table-driven cas