What problem does it solve?
It prevents documentation-only changes from being forced through heavyweight code-level pipelines (worktrees, cloud review, full gates) while still catching governance, conflict, and irreversibility risks that genuinely require escalation.
Core Features & Use Cases
- Intent Gating: Distinguishes review-only requests from authorized co-creation and landing, blocking writes, commits, and pushes when only feedback was requested.
- Risk-Based Classification: Runs a classifier with explicit conflict and reversibility inputs to decide between direct push, pull request, or regular development lanes.
- Independent Escalation Decisions: Treats PR creation, cloud review, and full gate as three separate conclusions rather than an automatic bundle.
- Use Case: When updating a long architecture document in docs/ with no conflicting PRs and a single reversible commit, the skill self-assesses direct push, runs lightweight incremental frontmatter validation, commits with a Why-focused message, and reports the SHA and push result.
Quick Start
Ask the assistant to review and land these Markdown documentation changes using the co-creation docs lane, classifying the risk before deciding between direct push and a pull request.
