code-review-business
Skill0 starsChanged 2 months agoMITView on GitHub
Use automatically when reviewing code, features, pull requests, product changes, funnels, SaaS flows, e-commerce flows, dashboards, landing pages, or app behavior where both technical quality and business impact matter.
In this repository5 other files it gives its agents.
- landing-page-conversionSkill
- project-launch-checkSkill
- release-checklistSkill
- security-liteSkill
- seo-ai-search-safeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when reviewing code or product changes that should not merely work technically, but also help the business.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Review Business-Oriented
Use this skill when reviewing code or product changes that should not merely work technically, but also help the business.
Review from two angles:
- Technical correctness
- Business usefulness
Technical checks
- Bugs
- Edge cases
- Type errors
- Broken flows
- Performance issues
- Security risks
- Error handling
- Data validation
- Auth/permissions
- API failures
- Logging and observability
- Maintainability
Business checks
- Does this help conversion, retention, clarity, revenue or trust?
- Is the user flow obvious?
- Is the CTA clear?
- Is there friction?
- Are analytics/tracking events missing?
- Is the feature understandable by a non-technical customer?
- Could this create support tickets?
- Does the change match the product goal?
Output format
- Executive verdict: ship / fix first / risky
- Highest-impact issues
- Technical issues
- Business/UX issues
- Missing analytics or measurement
- Recommended next changes
- What not to waste time on
Be direct. Do not flatter bad work. Prioritize what moves the product forward.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.