source-command-fix-build
Skill18 starsChanged 5 months agoMITView on GitHub
派遣 build-error-resolver 修复构建/类型/依赖/配置错误,不建 session
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when the user asks to run the migrated source command fix-build.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
source-command-fix-build
Use this skill when the user asks to run the migrated source command fix-build.
Command Template
/fix-build
轻量入口:只派 build-error-resolver,以最小 diff 让构建变绿。不做架构调整、不做功能修改、不顺手重构。
使用
/fix-build # 主会话从最近的失败诊断
/fix-build npm run build # 指定要修复的命令
/fix-build tsc --noEmit # typecheck 失败流程
- 主会话获取失败命令的完整输出(首次出问题就跑一次完整命令,捕获 stderr)
Agent({ subagent_type: "build-error-resolver", ... })派遣,传入:- 失败命令
- 完整错误输出
- 项目栈(package.json / pyproject.toml / go.mod)
- build-error-resolver 按
.Codex/agents/build-error-resolver.md输出"修复报告" - 主会话呈现 diff + 重跑证据(同一命令变绿)
边界
- 单一命令变绿即停,不顺手修其他失败
- 不修测试断言(除非断言本身错误且必须报告)
- 不做依赖大版本升级(除非失败信息明确要求)
In this repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fine-tuning-expertSkill
- ml-pipelineSkill
- rag-architectSkill
- spark-engineerSkill
- api-designerSkill
- architecture-designerSkill
- code-documenterSkill
- debugging-wizardSkill
- feature-forgeSkill
- fullstack-guardianSkill
- graphql-architectSkill
- legacy-modernizerSkill
- microservices-architectSkill
- database-optimizerSkill
- postgres-proSkill
- sql-proSkill
- csharp-developerSkill
- dotnet-core-expertSkill
- angular-architectSkill
- flutter-expertSkill
- nextjs-developerSkill
- react-expertSkill
- react-native-expertSkill
- senior-frontendSkill
- ui-ux-pro-maxSkill
- vue-expert-jsSkill
- vue-expertSkill
- cpp-proSkill
- golang-proSkill
- rust-engineerSkill
- cli-developerSkill
- cloud-architectSkill
- devops-engineerSkill
- kubernetes-specialistSkill
- mcp-developerSkill
- monitoring-expertSkill
- sre-engineerSkill
- terraform-engineerSkill
- websocket-engineerSkill
- java-architectSkill
- kotlin-specialistSkill
- javascript-proSkill
- nestjs-expertSkill
- typescript-proSkill
- spring-boot-engineerSkill
- spring-boot-engineer_znSkill
- laravel-specialistSkill
- php-proSkill
- competitive-analysisSkill
- meeting-notesSkill
- prd-templateSkill
- stakeholder-updateSkill
- user-research-synthesisSkill
- django-expertSkill
- fastapi-expertSkill
- pandas-proSkill
- python-proSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

