Claude-Code-Quest

The team's review of a change to linkcheck, run the same way on a laptop and in CI. Use on a staged diff or a pull request.

Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.

Builds a requested feature test-first, one behavior at a time, and stops at a diff for review. Use when the user asks for a new function or feature, or says test-first or TDD.

Adds a one-line entry for the staged changes to CHANGELOG.md. Use when the user asks for a changelog entry.

Runs the link checker on a folder and explains each broken link it finds, with the file, the line and a likely fix. Use when someone asks to check links or find broken links in the docs.

Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what stays personal, and what the team-kit plugin adds. Use when someone asks how the team's Claude Code setup works or what they get by cloning the repository.

The team's checklist for reviewing a change to linkcheck. Use before you commit or open a pull request.