github-writer

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

* When pushing a commit:
  * if the PR already existed and was opened by your GitHub account, update the description if needed.
  * If this is the last commit you will push:
    1. Rebase with the default branch if GitHub reports merge conflicts.
    2. Wait until CI is green.
    3. If CI fails and your changes introduced the failure, fix it and push again.
    4. If CodeRabbit is configured, wait until it posted its review.
       If CodeRabbit stopped reviewing this PR, trigger the review yourself.
       If CodeRabbit doesn't work (eg it is rate-limited), ignore it.
    5. Address all reviews/finding (by humans or bots) that you think are necessary.
       Verify every finding against the latest version of the source.
       If you agree, push a commit, if you disagree, reply explaining why.
* When opening a PR, open it in draft.
* When you are explaining how you validated your work, don't mention verification steps verified by CI.
* Before writing anything (PR title, PR description, comments, etc), check for secrets and private details.

## Watching PRs on T3 code: `watch_pull_request`

If available, use the T3Code mcp tool watch_pull_request to wait for PR updates.

Handle the existing checks and comments first. Then call
`watch_pull_request` and end your turn. T3 Code wakes you with a message when
a check fails, the required checks pass, someone comments or reviews, or the
branch conflicts.

- **Only the thread that owns the PR watches it.** If you are a delegated
  child task (a reviewer, any `delegate_task` child), never call
  `watch_pull_request`. The parent owns the PR. Do not watch PRs you are not
  working on.
- **A wake is news, not a merge decision.** Check the merge gate yourself.
- **Unwatch when you hand off.** A watched thread stays in Working and out of
  the user's inbox. When you stop (ready, blocked, or asking the user a question),
  call `unwatch_pull_request` first. A merge or close ends the watch on its
  own.
- **"Stopped watching, could not read it"** usually means GitHub's rate limit
  is used up. Run `gh api rate_limit --jq .resources.graphql` before you
  watch again. If `remaining` is near 0, wait for `reset` with one background
  command, then watch again. Never watch again in a tight loop.

From marcoieni/skills, MIT.

More from marcoieni/skills