Add or update a focused, reusable test when fixing bugs or changing behavior. Keep it in the project's existing test structure, verify the relevant change, and maintain coverage as the expected behavior evolves.
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable. It keeps the smallest focused test with the delivered project and updates coverage when behavior changes. Do not load for greenfield work unless reusable tests are explicitly required, behavior-preserving refactors, verification-only work, plan/review/explanation/documentation/formatting/generated-output-only work, explicit no-change or no-tool work, or when the user declines tests.
Review the instructions the agent will receive before you install.
Verification is part of the delivered project when it can prevent the same behavior from breaking again. Use the project's existing framework and conventions.
For a bug fix or behavior change, add or update the smallest maintained test in the repository's normal test layout that exercises the changed behavior. If a specification makes a reusable suite or test category a deliverable, implement that suite instead of treating it as private verification.
An inline interpreter command, heredoc, scratch script, temporary-directory test, demo, or manual probe may help diagnose the problem, but it does not replace the maintained test. Keep a useful self-authored test unless the user explicitly asks for a disposable probe.
Do not add a new test framework solely to satisfy this skill. If the repository has no maintained harness and the request does not require one, disclose when durable coverage would be disproportionate or infeasible and use the narrowest honest verification instead.
On a later turn, update the maintained test even when the old suite remains green and the user does not repeat the test request. Cover the new behavior, not merely an unrelated cleanup in the test file.
Observe the authentic failure before the implementation change when it is safe and runnable. Then make the smallest implementation change and run the focused maintained test after the final relevant source or test edit.
Do not weaken or delete a real failing test to obtain green. Fix the product, or explain why the test's expectation is wrong before changing that expectation. Do not repeat an unchanged check solely to collect evidence.
Run a broad or full suite only when the user, a repository gate, or proportionate risk requires it. A focused regression test comes first; broad proof does not substitute for missing focused coverage.
If the real runner is unavailable but the focused test can still be authored honestly, leave the focused test in the repository and say it was not run. Do not fabricate a passing result.
No reviews yet. Tell others what you thought.
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.
Create a 3D object with three.js, inspect it from every angle in an interactive viewer, and download it as OBJ + MTL or GLB for use in other 3D applications.
Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.
Coordinate a task from a verifiable goal through completion. Handle work directly or split independent tasks across separate agent sessions, track progress, verify results, and arrange pull request merging when included in the goal.
Create animated HTML pages with smooth scene transitions and playback controls. An editable timeline lets users adjust scene lengths and speeds, with fixed landscape or portrait layouts prepared for video export.
Review synced Apple Health records, including steps, heart rate, sleep, and workouts. Retrieve daily summaries or detailed samples for a chosen period, and check sync status and missing data before interpreting the results.
Create and edit Word documents and templates, reorganize text, replace images, and work with tracked changes or comments. Apply proper headings and lists, then render every page to check its appearance before delivery.