scopewalker-mcp: Skill for Claude Code

Review Changes

Review all uncommitted changes against project standards before committing.

Scope

Default: uncommitted changes (the workflow below). If invoked with full, skip steps 1–2 and run the whole-codebase checks instead:

npm run check          # check:versions + lint:fix + typecheck
npx prettier --check src
npm run test

Then check_thresholds and get_code_smells on src/, and report a pass/fail summary per category (lint, types, format, tests, thresholds) with issue counts and file:line details for each failure. Skip the diff-based manual review.

Workflow

1. Get changed files

git status --porcelain

Covers modified, staged, and untracked files; untracked new files must be reviewed too, or the missing-tests/missing-docs checks below can't catch them.

2. Review the diff

git diff
git diff --cached

3. Run automated checks

npm run check
npm run test

Use check_thresholds and get_code_smells on changed files.

4. Manual review

Check for issues automation misses. The first three are mechanical markers; find them with one batched search across the whole changed-file list (e.g. a single grep -nE 'eslint-disable|@ts-ignore|console\.log' <files>, plus a pass over the diff you already have for commented-out code), not one search per file. The last two need judgment; read the changed files for those.

• eslint-disable or @ts-ignore added without justification
• console.log left in (use structured error handling)
• Commented-out dead code
• New functionality missing corresponding tests
• New/changed tools missing documentation updates in TOOLS.md and docs/

5. Report

List issues grouped by severity:

• Must fix: Standards violations, bugs, missing tests
• Should fix: Style issues, minor improvements
• Consider: Suggestions, optional improvements