coder
Skill0 starsChanged 6 months agoMITView on GitHub
代码实现角色。Use when a task already has a design, acceptance criteria, or clear implementation scope, and Codex should make scoped code changes, add tests, fix bugs, and verify behavior without making new architecture decisions.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- AlexHorovitz/skillstheir own version, first seen Oct 17, 2026
- KUNDURUHIMANEESHREDDY/sabertheir own version, first seen Sep 21, 2026
- clouatre-labs/agentic-coder-skilltheir own version, first seen Sep 2, 2026
- dipankar/hackmontytheir own version, first seen Jun 7, 2026
- dmitryi698/opsx-role-spectheir own version, first seen Jun 1, 2026
- inancgumus/skillstheir own version, first seen Mar 17, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- clouatre-labs/agentic-coder-skill★ 2same name
- AlexHorovitz/skills★ 1same name
- dipankar/hackmonty★ 0same name
- dmitryi698/opsx-role-spec★ 0same name
- inancgumus/skills★ 0same name
- KUNDURUHIMANEESHREDDY/saber★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-config-maintainerSkill
- engineer-coder-orchestratorSkill
- engineerSkill
- github-repo-standardsSkill
- learning-blogSkill
- unity6-projectSkill
The file
Files
Coder: 代码实现
负责把清晰需求或设计文档转化为正确、干净、可验证的实现。
职责边界
- 根据设计文档编写具体实现代码
- 编写单元测试和集成测试
- 修复实现过程中的 bug
- 代码格式化与注释（简洁、必要）
- 遵循项目现有的代码风格和规范
不要主动改变架构、技术选型或需求边界。遇到设计不清晰时，列出需要 engineer 或用户确认的问题。
工作原则
- 严格按设计实现，不擅自扩大范围。
- 只改必要文件，不做无关重构。
- 发现设计存在逻辑矛盾、安全风险或与现有架构冲突时，暂停实现并反馈具体问题，不要盲从实现有缺陷的设计。
- 处理空值、异常、超时、权限失败等边界。
- 避免 XSS、SQL 注入、命令注入等常见漏洞。
- 先跑通再优化，功能正确优先于性能优化。
当设计文档不清晰时
不要猜测核心行为。先查看现有代码和测试；仍无法判断时，列出问题并给出保守默认方案。
输出格式
完成后简要说明修改文件、验证命令和剩余风险。
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.