- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill fix-bug -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill fix-bug -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill fix-bug -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill fix-bug -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/Doist/todoist-cli/tree/HEAD/.agents/skills/fix-bugFrom the publisher
Write down what happens, what should happen, and the command that triggers it (td <command> <args>). If the report is vague, restate it to the owner and ask before going further. Done when the symptom fits in one sentence.
Write a test that fails on the exact symptom, at the lowest layer that shows it:
src/lib/ → its *.test.ts next to it;program.parseAsync(['node', 'td', ...]) with setupApiMock();src/index.integration.test.ts.Follow write-tests for helpers and the quality bar. Run the test and see it fail for the reason in step 1, not a typo or a missing mock. Done when the failure message describes the bug.
Trace from the symptom to the first place the data goes wrong. Name it with path:line. A fix at the symptom (a special case, a retry, a try/catch) is not a root cause. Done when you can say why the code does what it does.
Change only what the root cause needs. Note other bugs you find for a separate fix; don't fix them here. Restructuring goes to refactor, as its own change.
Undo the fix: the test fails. Restore it: the test passes. Then npm run verify. Done when you have seen both and verify prints Verified.
After three fixes that didn't turn the test green, stop. Your model of the bug is wrong. Re-read the failing output, question the test, and list what you have ruled out before trying again. Tell the owner if you're stuck.
Use the verify report format. Include the test name, the root cause line, and the undo/restore result.
Fixes a bug by reproducing it in a failing test first, then making the smallest change that turns it green. Use when something is "broken", "wrong", "fails", "doesn't work", throws an error, or a user
---name: fix-bugdescription: Fixes a bug by reproducing it in a failing test first, then making the smallest change that turns it green…---# .agents/skills/fix-bug/SKILL.mdOverview
Fixes a bug by reproducing it in a failing test first, then making the smallest change that turns it green. Use when something is "broken", "wrong", "fails", "doesn't work", throws an error, or a user or issue reports a bug.
FAQ
Download .agents/skills/fix-bug/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/Doist/todoist-cli.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.