Menü
OpenAgentd workflow for well-formatted, detailed conventional commits.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
OpenAgentd workflow for version bumps, release PRs, GitHub releases, and release notes.
Select and create accurate software architecture, workflow, interaction, data, state, and deployment diagrams.
OpenAgentd workflow for keeping the compact feature catalogue and README aligned with user-visible changes.
Research first, propose a step-by-step implementation plan, and wait for explicit approval before writing any code.
Semantic search over the retained OpenAgentd feature catalogue, ADRs, and repository instructions using the turbovec experiment index.
OpenAgentd TDD workflow — write a failing test before the code that makes it pass, reproduce a bug with a test before fixing it. Use when implementing any logic, fixing any bug, or changing any existing behavior in backend (pytest) or frontend (Bun/RTL) code.
| 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 |