developer-coding
Structured workflow for implementing code changes in a conversation's code folder.
Informations de source
- Dépôt
- siddsachar/row-bot
- Dernière activité de la source
- 1 octobre 2026 à 08:06
- Langue détectée de SKILL.md
- anglais
- Étoiles
- 1 686
- Forks
- 204
Options d'installation
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Vérifiez les fichiers source
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Affichage de SKILL.md
SKILL.md
Instructions source · Aperçu en lecture seule- name
- developer_coding
- display_name
- Developer Coding
- icon
- code
- description
- Structured workflow for implementing code changes in a conversation's code folder.
- enabled_by_default
- false
- version
- 1.0
- tools
- ["developer"]
- tags
- ["developer","coding"]
- author
- Row-Bot
# Developer Coding
Use this skill when the user asks, in a conversation with a code folder, to add, fix, refactor, or test code in a repository.
Work in this order:
1. Confirm the active workspace, branch, approval mode, and dirty state.
2. Create or update a concise todo plan for anything beyond a tiny edit.
3. Read the smallest set of files that explains the behavior.
4. Make surgical edits with Developer-native write or patch tools so the Inspector can track them.
5. Respect execution mode. In Docker Sandbox mode, edits and commands create pending sandbox changes; import them into the real repo only after the user approves.
6. Run focused tests first. Broaden test scope when the change touches shared behavior.
7. Review the final diff and explain what changed, what passed, and what remains unverified.
Keep progress visible. Before a long inspection, edit, or test cluster, write a short sentence telling the user what you are doing.
Voir sur GitHub