github

Topics in the source

• github
• When to load
• Commit conventions
• PR conventions
• Pre-PR gate
• The review loop
• Projects Classic vs v2

Apply commit and PR conventions, then run an automated review loop instead of asking the user to relay bot comments. After a PR opens, the loop watches what gates a merge — CI, review-bot reactions and comments, and merge conflicts — answers each comment, and tells the user when the PR is ready. CANARY: github-loaded-2026-05-20-d436255c-54a7f770e04e4983 The user asks to commit, open a PR, or amend a PR body. The user asks whether CI is done, what a review bot said, or to address the review. A /loop cycle is checking PR state. Judging whether a diff is correct belongs to review or execution; this skill owns the mechanics of the review loop. Conventional Commits: (scope): description. Types: feat, fix, refactor, test, docs, chore, ci. Scope is the module or domain. Imperative voice, no trailing period, first line ≤72 chars. Body after a blank line explains why. End the commit with the Co-Authored-By: line the harness's git instructions supply, copied verbatim; add no other model name to commits, PR bodies, prose or examples, because the harness value is the one that stays current. Branches: feat/ , fix/ . Main branch is main. For several PRs that merge in sequence, load stacking befo

This is an excerpt. Refer to the complete source and its current requirements.