What problem does it solve? When AI agents open, review, and merge pull requests on GitHub, GitLab, or Forgejo, PR bodies often leak process-internal references, merges bypass consent, and out-of-scope findings vanish without a durable record. This Skill defines the discipline that keeps the forge a clean, self-contained public record. ## Core Features & Use Cases - Branch-to-PR mapping: Defines per-node PRs against a shared integration branch plus one tracking PR per campaign, including the forced bootstrap order and stacked PR handling. - Self-contained PR prose: Enforces a two-question test (what is this work, how do I review it), soft-wrapped formatting, SHA-pinned permalinks, and a mechanical check_forge_prose.sh gate before posting. - Merge consent and git-only merges: Merges happen in the git CLI with the head's explicit consent; the forge observes and records but never performs the merge. - Forge audit and tracking issues: A composer-owned checklist at merge-consent and campaign close, plus meta tracking issues and mandatory criticality labels for out-of-scope findings. - Use Case: An agent finishing a campaign node pushes its branch, opens a node PR with self-contained prose, posts review findings as impersonal comments, merges locally in git after consent, and files every deferred finding as a linked, tagged issue. ## Quick Start Use the forge skill to draft a self-contained PR body for my current branch and check it with the forge prose gate before opening the pull request.