Skip to content
cccskills
FreePublished on GitHub

investigate-and-fix

Diagnose and fix the bug described on this card

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Your task: Investigate and fix

If you don't already have this card's context (title, identifier, description) — for instance when running outside Workhorse — establish it first by following .agents/docs/card-context.md.

The card describes a bug. Diagnose the cause and apply the fix.

  1. Read the card — title, description, reproduction steps, error messages, attachments. Treat these as the report
  2. Locate the code path — use the existing specs in specs/ to understand the intended behaviour, then find the code that implements (or should implement) it
  3. Form a diagnosis — what the code currently does, what it should do, and why the two diverge. State this in chat before touching code so the user can agree or redirect
  4. Apply the fix — edit the code so it matches the intended behaviour
  5. Decide about the spec — bug fixes usually don't require spec updates, but if the bug existed because the spec was unclear, wrong, or missing, update the spec first so it reflects the intended behaviour, then fix the code to match (see .agents/docs/spec-format.md)
  6. Summarise the diagnosis and the fix in the conversation — short, specific, with file references

If the description is too thin to diagnose confidently, ask the user for the missing reproduction details before guessing.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Check whether this card's code meets the acceptance criteria

The English summary is being prepared. Showing the original description.

beyondessential/tamanu9Updated Oct 23, 2026

Summarise the unit and e2e tests a branch/PR adds, run only those, and produce a paste-ready report (e.g. for a Linear card). Use when asked to 'summarise added tests', 'run the new tests', 'what tests did this PR add', or to prove a card's test coverage.

The English summary is being prepared. Showing the original description.

beyondessential/tamanu9Updated Oct 23, 2026

Run a quick UX/UI workshop using ASCII-art sketches

The English summary is being prepared. Showing the original description.

beyondessential/tamanu9Updated Oct 23, 2026

Write automated tests for unticked scenarios in this card's test cases

The English summary is being prepared. Showing the original description.

beyondessential/tamanu9Updated Oct 23, 2026

Review code changes on this card for likely bugs, regressions, and missed edges

The English summary is being prepared. Showing the original description.

beyondessential/tamanu9Updated Oct 23, 2026

Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.

The English summary is being prepared. Showing the original description.

beyondessential/tamanu9Updated Oct 23, 2026

See all skills by beyondessential

Report a problem with this skill