archify-review — Claude Code skill: reviews code and PRs
The archify-review skill weighs issues, pull requests, and code by value, cost, and impact. Use it for triage, change reviews, and maintenance decisions.
Apache-2.0 ★ 98,599 updated 2026-10-25
npx skills add tt-a1i/archify --skill archify-review -a claude-codeWhat archify-review does
The skill examines an issue, pull request, or code through value, cost, and impact. It asks what problem the work addresses, who benefits, how often it matters, and whether the work is worth doing now. The review also considers implementation and verification effort, future maintenance, affected modules, and added coupling.
The agent is instructed to verify the target revision and relevant facts, separating direct checks from existing evidence and assumptions. It then explains the approach’s cost and consequences, points to better alternatives where relevant, and lists unresolved questions that affect the decision. Complexity, compatibility, performance, and maintainability are considered according to the case.
Repository-specific contribution guidance can be checked in REVIEWING.md and CONTRIBUTING.md. A review that skips verification of the target revision has weaker grounds.
What it helps with
- triage an issue before committing to it
- review a pull request by value, cost, and impact
- trace a change’s effects across modules
- compare an implementation with simpler alternatives
- surface unresolved questions before maintenance work
Example prompts for the agent
- Assess this issue: who benefits, how often does it occur, and is it worth addressing now?
- Review this pull request for its value, implementation cost, and impact on affected modules.
- Check the target revision, evaluate this approach, and list better alternatives and open questions.
How to install archify-review
1Skills CLI (Vercel)
npx skills add tt-a1i/archify --skill archify-review -a claude-code2Manually: put the files in place
~/.claude/skills/archify-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/archify-review/
1Skills CLI (Vercel)
npx skills add tt-a1i/archify --skill archify-review -a codex2Manually: put the files in place
.agents/skills/archify-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tt-a1i/archify --skill archify-review -a cursor2Manually: put the files in place
.cursor/skills/archify-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tt-a1i/archify .agents/skills/archify-review2Manually: put the files in place
.github/skills/archify-review/SKILL.md1Skills CLI (Vercel)
npx skills add tt-a1i/archify --skill archify-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/tt-a1i/archify --path .agents/skills/archify-reviewManually: put the files in place
.devin/skills/archify-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about archify-review
How do I install archify-review in Claude Code?
Run npx skills add tt-a1i/archify --skill archify-review -a claude-code, then check ~/.claude/skills/archify-review/SKILL.md.
What does archify-review do?
It reviews issues, pull requests, and code by weighing value, cost, and impact. The result separates verified facts from assumptions and supports a maintenance decision.
Which platforms support archify-review?
The skill is intended for Claude Code and Codex.
Source text
SKILL.md · Apache-2.0
--- name: archify-review description: Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and code quality assessments. metadata: internal: true --- # Archify Review Judge whether a problem is worth addressing and an approach is worth maintaining over time. - **Value**: Identify the real problem, who benefits, how often it occurs, its consequences, and whether it is worth addressing now. - **Cost**: Consider implementation and verification effort, along with the future cost of understanding, changing, and maintaining the code. Prefer existing capabilities and keep the solution proportional to the problem. - **Impact**: Identify affected behavior and modules, consequences for users and future development, and whether the change improves maintainability or adds coupling and constraints. Consider maintainability, complexity, compatibility, performance, and other relevant concerns within these three dimensions, according to the specific problem. Ground judgments in evidence: verify the target revision and relevant facts, distinguish direct verification from existing evidence and assumptions, and choose checks that resolve the key uncertainties. Explain whether the work is worthwhile, the approach's cost and impact, any better alternatives, and unresolved questions that matter to the decision. Give reasons and scale the detail to the importance of each concern. For repository-specific review and contribution requirements, consult [REVIEWING.md](../../../REVIEWING.md) and [CONTRIBUTING.md](../../../CONTRIBUTING.md) as needed.
© tt-a1i · Apache-2.0 · tt-a1i/archify