Skip to content

oliver-kriska/claude-elixir-phoenix / targets/amp/skills/phx-review

phx-review

Verified

Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.

references/requirements-detection.md

View on GitHub
# Requirements Detection

Use this order and stop at the first usable source:

| Priority | Source | Detection | Fetch |
|---|---|---|---|
| 1 | Explicit path | User input ends in `.md` and the file exists | Read the file |
| 2 | Explicit issue ID | Input matches `^[A-Z]+-\d+$` or `^#?\d+$` | Available Linear integration or `gh issue view` |
| 3 | Conversation context | Requirements already appear in the session | Reuse them |
| 4 | Branch name | Branch contains an issue-like identifier | Available integration or `gh` |
| 5 | Commit subjects | Recent subjects contain an identifier | Available integration or `gh` |
| 6 | Latest plan | Relevant `.claude/plans/*/plan.md` exists | Read the file |
| 7 | None | No source found | Mark `NOT AVAILABLE` and continue |

Never let a missing Linear, GitHub, MCP, hook, or network integration block the
review. Record the selected requirements source and any fetch failure. Do not
silently substitute guessed requirements.

## Coverage Output

For each acceptance criterion, report `MET`, `PARTIAL`, `UNMET`, or `UNCLEAR`
with changed-file evidence. Put requirements coverage before code-quality
findings. Any `UNMET` criterion requires a `REQUIRES CHANGES` verdict; `PARTIAL`
without `UNMET` downgrades `PASS` to `PASS WITH WARNINGS`.
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall