code-review-impact-analysis
Skill0 starsChanged 4 months agoNo licenceView on GitHub
对实际代码修改做 finding-first review,检查行为缺陷、回归、低概率高影响放大风险,以及是否偏离需求、方案或项目约束,并输出影响面分析、验证状态和测试建议。适用于代码已完成或已有 diff 可审查的场景。
In this repository28 other files it gives its agents.
- ai-session-log-miningSkill
- api-integration-adapterSkill
- code-implementationSkill
- code-scope-identificationSkill
- commitSkill
- delivery-summarySkill
- implementSkill
- jiancai-domainSkill
- launchd-automationSkill
- llm-batch-resilienceSkill
- mastergo-react-design-to-codeSkill
- mastergoSkill
- mastergo-ui-fidelity-reviewSkill
- paircoderSkill
- planningSkill
- platform-scaffoldSkill
- platform-uiSkill
- repo-publish-safetySkill
- req-reportSkill
- requirement-clarificationSkill
- requirement-to-code-pipelineSkill
- review-fix-loopSkill
- skill-controllerSkill
- skill-governanceSkill
- solution-boundary-reviewSkill
- task-planning-and-solution-designSkill
- verifySkill
- webview-touch-scroll-debugSkill
The file
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.

