Handle git tasks with conventions
gitcommandsetup L1★158
fmflurry/settings-opencode ↗What it does
Handle git workflow with naming convention enforcement
Best for
Enforced git workflow: branch names (type/scope-description), commits (conventional format), avoids destructive ops, detects and prevents secret commits.
Inputs
- · git action (commit/branch/PR)
Outputs
- · commit or branch created
- · PR URL if applicable
Requires
- · git
- · gh
- · az repos
Preconditions
- · git repo initialized
- · branch/commit naming rules defined
Failure modes
- · invalid branch/commit format
- · file contains secrets
- · no matching PR found
Trust signals
- · explicit format rules for branches and commits
- · scope is required for branches
- · checks for secrets before committing
- · supports GitHub and Azure DevOps