Set up skills
Skills are the instructions the AI follows. CodeCrab creates them for each repository from your actual code.
Open Settings → Skills by repository and select the repo under Active repository.
5.1 Review Profile — automatic
- • Generated once the repo has a local path. It scans the codebase, CI and conventions and may take a few minutes.
- • View Profile shows its rules. Evidence shows where each rule came from.
- • Use Regenerate after major changes. CodeCrab warns when a profile is 30+ days old.
5.2 Master Review Agent — always on
The main reviewer runs on every review. Click View Skill File to read it. Nothing needs configuring.
5.3 CodeCrab review skills
Extra review passes are generated independently after the Review Profile is ready.
| Skill | Default | Use it for |
|---|---|---|
| Repo-adapted peer review | On | A second reviewer that knows your repo’s conventions. |
| Security review | Off | Auth, injection, secrets and data exposure. |
| Test completeness review | Off | Missing or weak tests for the change. |
Enable skills with their checkbox. View skill explains its scope and source. Regenerate rebuilds one skill without touching the others.
5.4 Reuse your own skills
Existing Claude Code skills in .claude/skills or ~/.claude/skills appear under Your own review skills. Select one to run it on every review.
- Click Template prompt to create your local skill.
- Copy the prompt and paste it into Claude Code inside your repo.
- Let Claude create
.claude/skills/review-peer-pr/SKILL.md. - Reopen the tab and select the new skill.
## Output format (CodeCrab contract — mandatory)
The final answer MUST use exactly this markdown shape. Keep the field labels in English. Do not
invent other section names (no "Critical Issues" or "Required Changes" headings).
```markdown
## Review Summary
**Verdict:** APPROVE | REQUEST CHANGES
**Overview:** 1-2 sentences.
**Stack context:** languages/frameworks/conventions inferred.
### Findings
#### Finding 1 — Critical|Required|Optional|Nit
- **File:** `path/to/file.ext`
- **Line:** 42
- **Axis:** Correctness | Readability | Architecture | Security | Performance
- **Problem:** Precise issue.
- **Why it matters:** Concrete merge risk.
- **Suggested fix:** Concrete change.
- **Detail ref:** codecrab_peer_review#1
- **Suggested PR comment:**
```
<copy-paste review comment addressed to the author; not posted>
```
```
Order findings: Critical, Required, Optional, Nit. Renumber from 1.5.5 Additional notes
Add context every review should know, such as “we’re migrating off Redux” or “ignore the legacy folder,” then click Save & sync.