demand-first-review

by CherryHQ 51k AGPL-3.0-only Updated Aug 18, 2026
demand-first-review skill by CherryHQ
Social preview for CherryHQ/cherry-studio

demand-first-review is an open-source backend skill for Claude Code and compatible agents, published by CherryHQ. Its author describes it as: “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 spec…”. The project has 51k stars on GitHub and is available under the AGPL-3.0-only license. Add it to your setup with `git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/demand-first-review`.

What demand-first-review does

Audit this causal chain before implementation quality:

Installation

Add demand-first-review to your agent with:

git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/demand-first-review

Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.

What's inside

The SKILL.md for demand-first-review is organised into these sections:

  • 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

When to use it

Reach for demand-first-review when you want backend help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.

Strengths

  • Clear AGPL-3.0-only license — safe to read and adapt
  • Ships in CherryHQ/cherry-studio, an established project with 50,722 GitHub stars
  • Actively maintained (recent commits)

Topics

agent-skillsai-agentclaude-codecodexdeepseekdeepseek-harnesshermes-agentskillsvibe-coding

Frequently asked questions

What does demand-first-review 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 demand-first-review?
Run git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/demand-first-review in your agent, then reload your skills. Review the source at https://github.com/CherryHQ/cherry-studio before installing.
Is demand-first-review free to use?
Yes. demand-first-review is free and open source under the AGPL-3.0-only license, so you can read, run, and adapt it within that license's terms.
Where does demand-first-review come from?
demand-first-review ships inside CherryHQ/cherry-studio, a repository that contains 20 catalogued skills in total. The repository's 50,722 GitHub stars apply to that whole collection, not to this skill on its own.

Related skills

More Backend →

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

51k CherryHQ AGPL-3.0-only

查询 AIHOT 的中文 AI 资讯、精选、当前热点和日报。用户询问今天或最近的 AI 新闻、AI 圈动态、大模型或产品发布、OpenAI/Anthropic/Google 最新消息、AI 论文、AI 日报、AIHOT 精选、当前最热事件,或需要同步当前全部精选时使用。必须通过 aihot.virxact.com 的匿名只读 API 获取当前数据,不凭训练记忆回答新闻;不需要 API Key 或 MCP server。

20k KKKKhazix MIT

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

88k addyosmani MIT

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

88k addyosmani MIT

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

39k wshobson MIT