Skip to content

wesammustafa/Claude-Code-Quest / solutions/a-capstone/dot-claude/skills/team-review

team-review

Verified

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.

Review the change you are given (a staged diff on stdin, or the pull request's diff) and change no file.

Report each finding as file:line and why, in this order:

  1. A bug: a link that would be reported wrongly, or a crash on some input.
  2. A changed function in src/ without a test in test/ that fails without the change.
  3. An error message that doesn't start with linkcheck: or doesn't say what to do next.

If you find nothing, say so in one line.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall