reviewer-base
Code reviewer shared rules — context, SonarQube, commit style.
SKILL.mdskills/shared/reviewer-base/SKILL.md
GitHubFoundational Rule
Load
skills/shared/project-context/SKILL.md— covers README, CLAUDE.md, AGENTS.md, project.md, session-summary, code-standards, architecture, and recent git log.Additionally for review sessions:
- Read linter configs (
.eslintrc*,pyproject.toml,.rubocop.yml,phpcs.xml,golangci.yml) — source of truth for style - Run
git diff main...HEAD --statfirst to see the size and shape of the change. Under ~15 files / ~800 lines, follow with a singlegit diff main...HEADfor full content. Above that, do not pull the whole diff into context in one call — review file-by-file with targetedgit diff main...HEAD -- <path>calls (or batches of a few related files), so one oversized diff never inflates a single turn enough to risk a context/prompt-size failure. Either way, focus all findings on what changed, not pre-existing code - Load
skills/shared/comments-policy/SKILL.md - Load
skills/shared/conventional-commits/SKILL.md - Load
skills/shared/scoped-test-execution/SKILL.mdbefore running any test command — a review that verifies behaviour runs the tests covering the diff, never the project's full suite. Reviewing is not one of the signals that authorize a full run - Report findings in
skills/shared/review-result/SKILL.md§ Findings Table; a zero-findings verdict follows § Clean Verdict Evidence, so plan the checks you will execute before you start reading - Detect SonarQube using the
## Detection Signalstable inskills/devops/sonarqube/SKILL.md— if any signal in that table matches, load the skill. That table is the single source of truth; do not maintain or infer a signal list here, and do not treat the config files as the only trigger (a CI scanner step or asonarqubeservice indocker-compose.ymlcounts too).
- Read linter configs (
Apply skills/shared/token-efficiency/SKILL.md — prefer grep/head over full-file reads; use git diff output directly rather than re-reading changed files.
After loading this skill, apply skills/shared/reviewer-mindset/SKILL.md for the review mindset questions.