Skills & Plugins¶
BLIS development uses Claude Code skills for review workflows. Skills are checked into the repository and automatically available when you open the project with Claude Code.
Project Skills¶
| Skill | Location | Purpose |
|---|---|---|
blis-pr-review |
.claude/skills/blis-pr-review/ |
PR review: correctness, invariants (the full registry, not just INV-1–INV-19), rules (R1–R23), cross-path parity, preemption safety, Q/A probing phase |
issue-review |
.claude/skills/issue-review/ |
Issue validation: VALID / NEEDS WORK / SUPERSEDED / DUPLICATE verdict |
Project skills require no installation — they are checked into the repository and automatically available.
CI Integration¶
Both skills are triggered via GitHub Actions (@claude /blis-pr-review on PRs, @claude /issue-review on issues). Additionally, /archon-pr-review runs as a separate CI action for structural architecture review (boundary moves, surface changes, edge deltas). See Archon PR Review.
/blis-pr-review runs on a read-only token — it can post its review comment, but cannot push to the branch it is reviewing (the pass/fail commit status is published by a separate job). Every other @claude trigger keeps write access, since those may legitimately be asked to make a change. Do not widen the review token to work around a failure: see Agent Trust Boundaries.
Which Skills for Which Workflow¶
| Workflow | Skills Used |
|---|---|
| Bug fix / small feature | @claude /blis-pr-review + /archon-pr-review (FAST-TRACK) |
| Large feature (new boundaries) | Same review skills, plus archon --plan flag for dist tracking |
| Issue validation | @claude /issue-review |
Optional Plugins (user-level)¶
General-purpose Claude Code plugins can be installed per-user for enhanced workflows:
superpowers— worktrees, writing-plans, executing-plans, TDD, debuggingcommit-commands— git workflow (commit, push, PR creation)pr-review-toolkit— generic PR review
Install from marketplaces:
Installed plugins persist in ~/.claude/plugins/ and are available across all projects.