Menú
Agent Skill for safely handling the git commit process. Use whenever the user asks to create commits
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.
Basado en la clasificación ocupacional SOC
Agent Skill for planning implementation work into comprehensive, testable steps. Use before implementation to create a clear roadmap for execution.
Agent Skill for writing and reviewing durable design specs. Use when the user asks to write, formalize, save, review, or approve a spec, design document, RFC, or implementation-ready proposal. If the direction is still vague or unsettled, use `brainstorming` first before producing the spec. If the direction is already clear and no spec is needed, use `plan`.
Agent Skill for spawning new AI agents with interactive TUI in tmux. Use when work can be offloaded to new or existing AI agents (exploration, code review, second opinions, parallel work, etc.). Can also be used if spawning new agents with different model families (e.g. Spawn GPT models when you are Claude Code, Spawn Claude models when you are Codex, Or spawn any other models (e.g. DeepSeek, Gemini) with Pi). Prefer harness's own subagent tools when no need for a different model.
Agent Skill for OpenCLI. Use when the user wants to control websites through the `opencli` CLI, run or inspect OpenCLI site/app/external adapters, use the OpenCLI browser bridge/CDP automation
Agent Skill for collaborative brainstorming and design exploration. Use when the user wants to think through an idea, compare options, clarify trade-offs, or get a quick recommendation, without forcing a written artifact. If the user wants a saved, reviewed design spec, use `design-spec`.
Agent Skill for working with Python. Use when writing, editing, or reviewing Python code and scripts.
| name | commit |
| description | Agent Skill for safely handling the git commit process. Use whenever the user asks to create commits |
This skill handles the git commit workflow with a focus on logical grouping and clear documentation.
Analyze State
git status to identify all untracked, modified, and deleted files.git diff (unstaged) and git diff --cached (staged) to examine the actual code changes.Group Changes (Crucial Step)
Draft Commit Messages For each identified commit group:
gitmoji <type>(<scope>): <subject>
feat, fix, docs, style, refactor, test, chore.Execute Commits For each group:
git add <specific_files> (Do not lazy use git add . unless all changes truly belong to one commit).git commit -m "header" -m "body".env files.git status after operations to ensure the working directory state is what you expect.auth.py (bug fix), README.md (typo fix).git add auth.py -> git commit -m "🐛 fix(auth): resolve token expiration issue"git add README.md -> git commit -m "📝 docs: fix typo in installation guide"Title: ✨ feat(ui): implement dark mode theming
Body:
```text
- Add theme context provider
- Update color palette in tailwind config
- Add toggle switch to settings page
- Fix contrast issues on dashboard
```