Exercises
Skills
Finish a half-built bug-reporter skill and trigger it on a known bug.
Goal
Claude Code skills are reusable, opinionated prompts the agent picks up
automatically when the right kind of request shows up. This exercise has
you finish one skill end to end: a bug-reporter skill that turns a
casual bug description into a structured report.
Getting started
The repository ships a starter with one stub skill at
.claude/skills/bug-reporter/SKILL.md and one file with a known bug at
src/product-service.js.
claudeWhat you do
Open
SKILL.md and read the to-do list inside it.Finish the frontmatter description so Claude triggers the skill automatically when someone describes a bug.
Write the body. It should produce a report with title, steps to reproduce, expected vs actual, severity (with justification), and a suggested fix location. No code changes, no PR.
Trigger it. Ask Claude "report a bug: addProduct in product-service.js accepts a whitespace-only SKU". Confirm Claude picks the skill (without you naming it) and produces the structured report.
Repeat with two different source-backed descriptions to confirm the format holds up. For example, report that
addProduct accepts an empty name and that priceFor accepts a negative quantity. Do not invent behavior the file does not contain.Done when
- The skill triggers without you naming it.
- The output follows your template every time, on three different bug descriptions.
- You can name one other skill you would author at your job with the same shape (release notes, change-log entries, on-call summaries).