Menu
Git operations, branching strategy, commit conventions, and PR workflow. Use for all git operations. Enforces clean history and conventional commits.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
DEEP multi-step research harness. Decomposes queries into sub-questions, executes parallel web searches via Pieces MCP, iteratively refines with gap detection, and synthesizes cited reports. Architecture inspired by GPT Researcher (27.6k stars), Vane/Perplexica (35.2k stars), and Gemini Deep Research. Use when user asks for deep research, investigation, analysis, comparison, or any task requiring exhaustive web research.
DEFAULT THINKING MODE — not a feature, but how the agent operates. Every task gets innovation-overdrive thinking: research, ground, reflect on contradictions, propose, then build. This is the agent's identity, not a command. Integrates MiMo-Code's 6-phase memory consolidation.
Chain execution manager: validates dependencies, enforces order, tracks violations. Use to verify that all required skill chains were executed and to get the correct execution order.
API design patterns, REST conventions, and endpoint standards. Use when creating or modifying API endpoints. Covers routing, request/response patterns, error handling, and versioning.
Architectural design, system patterns, and dependency management. Use when designing new modules, refactoring existing systems, or making architectural decisions. Covers layering, coupling, cohesion, and design patterns.
Trigger-driven automation definitions and runner management. Use when creating, running, or managing skill-based automation pipelines.
| name | git-workflow |
| description | Git operations, branching strategy, commit conventions, and PR workflow. Use for all git operations. Enforces clean history and conventional commits. |
| chains_with | ["quality","automated-learning"] |
main # Production-ready, protected
└─ develop # Integration branch
├─ feature/* # New features
├─ fix/* # Bug fixes
├─ refactor/* # Code refactoring
└─ experiment/* # Experimental work
Use conventional commits:
<type>(<scope>): <description>
[optional body]
[optional footer]
| Type | Usage | Version bump |
|---|---|---|
feat | New feature | MINOR |
fix | Bug fix | PATCH |
refactor | Code change (no behavior change) | PATCH |
perf | Performance improvement | PATCH |
test | Adding/fixing tests | — |
docs | Documentation | — |
style | Formatting, linting | — |
ci | CI/CD changes | — |
chore | Maintenance | — |
revert | Revert a change | — |
BREAKING CHANGE: descriptionpytest tests/ -x -qruff check src/mypy src/## Description
[What this PR does]
## Type
- [ ] feat: New feature
- [ ] fix: Bug fix
- [ ] refactor: Code restructuring
- [ ] test: Test changes
- [ ] docs: Documentation
## Testing
- [ ] Unit tests added/updated
- [ ] All tests pass
- [ ] Manual testing done
## Breaking Changes
[None, or describe]
## Related Issues
Closes #[issue]
| Operation | Risk | Approval Needed |
|---|---|---|
| Force push | HIGH | NEVER on shared branches |
| Rebase shared branch | HIGH | Coordinate with team |
| Merge without review | HIGH | Emergency only |
| Delete remote branch | MEDIUM | Verify merged first |
| Amend push | MEDIUM | Only if branch is yours |