branch-cycle-audit

Audit Git branch ownership against cycle artifacts and enforce mapping validation.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/leuzeus/aidn --skill branch-cycle-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-cycle-audit
Source: https://github.com/leuzeus/aidn/tree/main/tests/fixtures/repo-installed-core/.codex/skills/branch-cycle-audit
Command: npx skills add https://github.com/leuzeus/aidn --skill branch-cycle-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify and enforce branch-cycle ownership to prevent drift between Git branches and cycle artifacts, ensuring predictable workflow state and ownership.

Core Features & Use Cases

  • Branch ownership verification: Determine the owning session/cycle artifact for current branches and prevent unowned or ambiguous branches from making writes.
  • Mapping enforcement and gating: Validate cycle/intermediate/session branch mappings against active cycles and enforce DoR requirements before commits.
  • Admission-aware workflow guards: Integrate with pre-write admission and DoR checks to halt workflows when ownership or mapping is unclear.

Quick Start

Identify the current Git branch and verify its ownership against active cycles, then update or confirm mapping as needed.

Frequently Asked Questions about branch-cycle-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent git branch drift during multi-branch workflow handoffs?

Prevent git branch drift by enforcing branch-cycle ownership through admission-aware gating, mapping validation against active cycles, and Definition of Ready checks before commits to ensure consistent workflow state.

What is branch-cycle ownership and when do I need to audit it?

Branch-cycle ownership is the verified mapping between a git branch and its owning session or cycle artifact. You need to audit branch-cycle ownership during session creation, branch creation, and cycle handoffs to prevent ambiguous or unowned branch writes.

How do I enforce Definition of Ready checks before commits in a git workflow?

Enforce Definition of Ready checks before commits by integrating admission-aware workflow guards that validate cycle and session branch mappings against active cycles, halting workflows when branch ownership is unclear or unmapped.

Can I block unowned git branches from making writes in a multi-branch workflow?

Yes, you can block unowned git branches from making writes by implementing blocking admissions that determine the owning session or cycle artifact for current branches and prevent writes when branch ownership is ambiguous or unowned.

Does branch-cycle mapping validation work with intermediate session branches?

Yes, branch-cycle mapping validation works with intermediate session branches by classifying per-branch types, validating intermediate mappings against active cycles, and optionally aligning snapshots to ensure a consistent state.