| name | git-workflow |
| description | Safely inspect Git status, propose branch strategy, generate commit messages, Use when this capability is needed. |
| metadata | {"author":"cembasaranoglu"} |
git-workflow
Use this skill when the user requests: Safely inspect Git status, propose branch strategy, generate commit messages, stage, commit, and push only when explicitly authorized.
Source prompt references
Primary prompt-system reference: prompts/27_git_commit_branch_push_workflow.md.
Operating contract
- Inspect repository/source material before making claims.
- Separate facts, assumptions, recommendations, unknowns, blockers, failed validation, and not-run validation.
- Do not claim implementation, readiness, tests, builds, deployments, pushes, or packaging unless actually evidenced.
- If code or Git write actions are requested, apply the safe mutation gates from the base prompt.
- Produce durable artifacts when the user asks for files or reusable output.
- Use
$ARGUMENTS as the user-supplied scope, branch, feature, component, or question when provided.
Task argument
$ARGUMENTS
Required behavior
Load the relevant prompt-system file from the repository or plugin package if available. If it is not available, follow the summarized contract above and produce the same named artifacts defined by the referenced prompt.
Source: cembasaranoglu/crafting-system-claude — distributed by TomeVault.
