yugasun Gitops
Git version control operations for the aiops delivery chain.
Operations
sync
Pull latest from remote. Default strategy: rebase.
git pull --rebase
If merge conflict: report to user, do not auto-resolve.
status
Show current working tree state.
git status
git diff --stat
stage
Stage files for commit. Supports selective staging.
git add <files>
commit
Create commit with Conventional Commits message.
Format:
<type>(<scope>): <subject>
<body>
Refs: .scratch/<feature-slug>/
Types: feat | fix | refactor | test | docs | chore
Message generation:
- Read
.scratch/<feature>/NOTES.mdfor design context - Read
.scratch/<feature>/REVIEW.mdto confirm review passed - Scope = feature-slug or module name
- Subject = imperative, lowercase, no period
- Body = reference upstream artifacts for traceability
Pre-commit checks:
- All blocking REVIEW.md findings resolved
- No untracked .scratch files in commit (add to .gitignore if needed)
push
Push to remote. Requires user confirmation.
git push origin <branch>
branch
Branch management: create, switch, list.
git checkout -b <branch> # create + switch
git checkout <branch> # switch
git branch # list
Flow
sync— pull lateststatus— review changesstage— select filescommit— with generated messagepush— after user confirms
Constraints
- Never modify code files
- Never auto-resolve merge conflicts
- Always confirm with user before push
- Commit message must reference .scratch artifacts when available
- If
.scratch/<feature>/REVIEW.mdexists and verdict is REQUEST_CHANGES, block commit and report