closed-loop-dev-migration
Skill0 starsChanged 5 months agoNo licenceView on GitHub
当用户需要将闭环研发方法论迁移到新项目时使用此 skill。 适用于任何需要长期迭代研发、有仿真/测试环境、需要视频或视觉反馈的项目。 读取项目核心文件，识别： - 项目的入口和启动流程 - 核心组件之间的依赖关系 - 数据/信号的流动方向 输出：信号链分层图（文本形式），通常 3-5 层： 列出项目所有可用的反馈信号： 确认以下能力： - [ ] 仿真/测试环境是否支持视频录制？ - [ ] 是否有现成的指标采集机制？ - [ ] 控制台/调度系统是否可编程？ - [ ]…
In this repository4 other files it gives its agents.
- dev-debuggerSkill
- integrate-algorithmSkill
- monthly-reportSkill
- session-to-docSkill
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.