archify-review

tt-a1i/archify · Agent Skill

A tool for analyzing issues, PRs, and code based on value, cost, and impact assessments. It supports evidence-based maintenance decisions, task prioritization, and software quality control.

Jump to install ↓

Overview

Publisher	tt-a1iCommunity
Repository	tt-a1i/archify ↗
Skill folder	`archify-review`
Stars	70,266
Forks	4,721
Bundled files	1
License	MIT
Last updated	September 23, 2026
Links	Skill source ↗ · Repository ↗

Mozgi check

What we found in the skill files. Details come with a subscription.

Security

low risk · no obvious risks found — the full report shows the details

Compatibility

instructions only — works with most agents

Similar skills

144 similar skills found

Also with subscription

Installation

A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.

Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.

Install the “archify-review” skill from mozgi.io (https://mozgi.io/skills/archify-review/) for me.

1. Download the archive: https://mozgi.io/skills/archify-review/download
   If it fails, take the skill folder from the source: https://github.com/tt-a1i/archify/tree/main/.agents/skills/archify-review
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “archify-review” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/archify-review/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

git clone --depth 1 --branch main https://github.com/tt-a1i/archify.git /tmp/archify
mkdir -p .claude/skills
cp -r /tmp/archify/.agents/skills/archify-review .claude/skills/archify-review

Restart Claude Code — the skill appears in the list; call it manually with /archify-review. For all projects use ~/.claude/skills.

git clone --depth 1 --branch main https://github.com/tt-a1i/archify.git /tmp/archify
mkdir -p .agents/skills
cp -r /tmp/archify/.agents/skills/archify-review .agents/skills/archify-review

Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $archify-review. For all projects use ~/.agents/skills.

git clone --depth 1 --branch main https://github.com/tt-a1i/archify.git /tmp/archify
mkdir -p .cursor/skills
cp -r /tmp/archify/.agents/skills/archify-review .cursor/skills/archify-review

Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.

git clone --depth 1 --branch main https://github.com/tt-a1i/archify.git /tmp/archify
mkdir -p .gemini/skills
cp -r /tmp/archify/.agents/skills/archify-review .gemini/skills/archify-review

Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.

Review the source files

1 file Download Zip

Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.

SKILL.md contents

Original author text · read-only

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 and CONTRIBUTING.md as needed.

Frequently asked questions

What does the archify-review skill do?

A tool for analyzing issues, PRs, and code based on value, cost, and impact assessments. It supports evidence-based maintenance decisions, task prioritization, and software quality control.

How do I install archify-review?

Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.

Which AI models work with archify-review?

Skills are plain Markdown instructions (the Agent Skills format), so archify-review works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.

Is archify-review free?

The skill is published openly by tt-a1i under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.

Is it safe to install skills?

A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.

How is a skill different from an MCP server or a plugin?

An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.

Related skills

All skills →

archify Generates interactive HTML diagrams for architecture, workflows, sequences, and data flows from text descriptions or Mermaid. Supports various export formats and themes. tt-a1i51.2k

agent-transcript Adds a redacted agent transcript to GitHub PR or issue bodies within OpenClaw agent-created workflows. openclaw389k

autoreview Automates code review using various AI models, providing structured reports and recommendations. openclaw389k

to-issues Breaks a plan or PRD into independently actionable issues. mattpocock304k

improve-codebase-architecture Scans a codebase for deepening opportunities and turns them into a prioritized visual report. mattpocock304k

triage Moves issues through a structured triage state machine. mattpocock304k