Branch ↔ Cycle Audit Skill
Goal
Prevent silent drift between Git branches and cycle artifacts.
Steps
- •
Identify current Git branch (if accessible). If not accessible, ask user to provide it.
- •
Scan active cycles: docs/audit/cycles/*/status.md Collect:
- •cycle id
- •state
- •branch_name
- •Check mapping:
- •If exactly one cycle has branch_name == current branch → OK
- •If none match:
- •suggest creating a cycle (cycle-create)
- •OR update the correct cycle status.md with branch_name
- •If more than one match:
- •warn: ambiguous mapping
- •ask user which cycle owns the branch
- •propose splitting branches or renaming
- •If current work mode is COMMITTING: Apply Branch/Cycle Requirement Auto-check:
- •Require a cycle + status.md
- •Require branch mapping in status.md (branch_name: ...)
- •Validate status DoR marker:
- •
dor_stateshould be READY - •if NOT_READY, ask user to resolve DoR gaps or explicitly document override reason
- •
- •Update snapshot (optional but recommended):
- •Ensure active cycle list reflects the mapped cycle
- •Next entry point points to that cycle status.md
Output:
- •Mapping result
- •Fix plan (if mismatch)