Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/lthoangg/OpenAgentd --skill oad-commitEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Update or upgrade the agent's own configuration on request — swap the model, add tools or MCP servers, change the image-generation provider/model, or install a new skill. Use when the user says things like "upgrade yourself", "switch your model to X", "use Gemini for images", "make yourself faster/smarter".
OpenAgentd testing reference — environment setup, run commands, and fix patterns for backend (pytest) and frontend (Bun/RTL). Load this for running, fixing, or adding coverage to existing tests. For writing a failing test before new code, use oad/test-driven-development instead.
OpenAgentd workflow for investigating bugs, regressions, sessions, and runtime issues.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | oad/commit |
| description | OpenAgentd workflow for well-formatted, detailed conventional commits. |
Git Commit Execution Workflow
git status --porcelain. If no files are staged, execute git add ..git diff --cached to evaluate the technical scope and architectural impact (e.g., DDD shifts or C4 updates).oad/docs to sync any documentation affected by the staged changes.<type>: <subject>git commit -m "<message>" and output the commit hash and a brief summary.Note: Multiple commits are preferred for large changes. If the scope is too broad, break it down into smaller, focused commits following the same workflow (do not force to have multiple commits if the change is small and cohesive).
Sizing: target ~100 changed lines per commit (a single logical, self-contained change); ~300 is acceptable for one cohesive change; ~1000+ should be split. Keep refactors and behavior changes in separate commits — mixing "renamed X" with "fixed Y" makes both harder to review and revert.
Commit Conventions
| Category | Type |
|---|---|
| Features | feat |
| Fixes | fix |
| Refactor | refactor |
| Maintenance | chore/docs |
| Style | style |