demand-first-review
Use when reviewing a PR, API, IPC channel, endpoint, parameter, type, config, or architectural extension point that adds or expands shared surface area, especially when consumers are absent, exports are unused or speculative, existing consumers are hack-heavy, forward compatibility is claimed, or multiple similar APIs may express one demand.
npx skills add CherryHQ/cherry-studio --skill demand-first-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Demand-First Review ## Principle Audit this causal chain before implementation quality: `root outcome or invariant → normalized demand → owning layer → contract → consumer` A call site proves usage, not legitimacy or shape. No call site raises the burden of proof, not an automatic rejection. Real demand may still have the wrong consumer or abstraction. ## Workflow Apply every step to each added API, channel, parameter, type, field, config, or extension point. ### 1. Reconstruct the demand List every new surface and exact consumed dimension; one valid consumer does not justify unused fields. Trace current and linked consumers to their user outcome, business rule, or system invariant. Inspect adjacent implementations, then ask: without the current API and history, would the demand remain and would this contract still be natural? Do not rely only on the PR description. ### 2. Audit consumer legitimacy - **Legitimate**: uses the correct owner and boundary. - **Compensating**: uses the nearest API and adds workarounds because the right capability is missing. - **Legacy-shaped**: reflects obsolete formats, transitional architecture, or history. - **Misplaced**: serves real demand in th
- Principle
- Workflow
- 1. Reconstruct the demand
- 2. Audit consumer legitimacy
- 3. Normalize related demands
- 4. Classify evidence
- 5. Test architectural demand
- 6. Check responsibility and overlap
- 7. Decide, then review implementation
- Rationalization Guards
- Red Flags
- Calibration
What does the demand-first-review skill do?
Use when reviewing a PR, API, IPC channel, endpoint, parameter, type, config, or architectural extension point that adds or expands shared surface area, especially when consumers are absent, exports are unused or speculative, existing consumers are hack-heavy, forward compatibility is claimed, or multiple similar APIs may express one demand.
How do I install it?
Run `npx skills add CherryHQ/cherry-studio --skill demand-first-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From CherryHQ/cherry-studio, a repository with 49,400 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.