archify-review

What problem does it solve? Maintainers often struggle to decide whether an issue is worth fixing or a change is worth merging. This Skill provides a structured, evidence-based framework for triaging issues, reviewing pull requests, and assessing code quality so maintenance decisions are grounded in facts rather than intuition. ## Core Features & Use Cases - Three-Dimension Evaluation: Judges every problem and approach through Value (who benefits, how often, consequences), Cost (implementation, verification, and long-term maintenance effort), and Impact (affected behavior, coupling, future constraints). - Evidence-Based Reasoning: Distinguishes direct verification from existing evidence and assumptions, and selects checks that resolve the key uncertainties before drawing conclusions. - Decision-Oriented Output: Explains whether the work is worthwhile, the approach's cost and impact, better alternatives, and unresolved questions that matter to the decision. - Use Case: When a contributor opens a PR adding a new feature, use this Skill to weigh its real user value against the maintenance burden it introduces, then produce a reasoned review verdict. ## Quick Start Review the open pull request for the new diagram export feature and assess whether it is worth merging based on value, cost, and impact.