You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f2864b8
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/create-pr/SKILL.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ A PR is one reviewable responsibility and may hold several atomic commits. A bra
15
15
2. Push and open the PR — `references/open-pr.md`. A squash merge writes the PR title as the commit subject on `main`, so CI holds the title to the same Conventional Commit scope rules the `commit` skill describes.
16
16
3. Request and handle AI review — `references/ai-review.md`, with the `gh` reply and thread-state calls in `references/gh-review.md`.
17
17
4. Watch CI after opening and after every push with `gh pr checks`. Read the failing step logs and annotations rather than the summary, then use the `fix-ci` skill for the fix, and ask the bots for another pass if they do not rerun on their own.
18
-
5. Merge only when the user explicitly asks and the conditions below hold: `gh pr merge <pr> --squash --delete-branch`. Squash is the repository's normal flow.
18
+
5. Merge only when the user explicitly asks and the conditions below hold: `gh pr merge <pr> --squash`, without `--delete-branch` or `--body-file`. On a base branch with a merge queue this adds the PR to the queue instead. When the PR fixes an issue someone else reported, credit that reporter with a `Co-authored-by` trailer on one of the PR's commits before merging, using their noreply address `<id>+<login>@users.noreply.github.com` (`gh api users/<login> --jq .id`): the squash body is built from the commit messages.
19
+
6. After merging, reply on each linked issue and on any original contributor PR it superseded. For a branch offered without a PR, reply where it was offered. Say what landed and in which PR, and, when it changes the published package, the release that shipped it or that it ships with the next one. Do this in particular when someone pinged or offered a branch and got no answer.
letcore_bug=issue-verdict-record'{"kind":"bug","maintenance_fit":"maintainable","confidence":"high","decision":"keep_open","priority":"priority:high","implementation":"create_pr","reason":"Confirmed cost calculation regression with a focused fix."}'true
619
-
expect'keeps a high-confidence core bug open'$core_bug.decisionkeep_open
631
+
(expect
632
+
'keeps a high-confidence core bug open'
633
+
$core_bug.decision
634
+
keep_open
635
+
)
620
636
(expect
621
637
'allows an important maintainable bug implementation'
0 commit comments