Using GitHub
Read docs/issue-tracker.md at the repository root before any issue work. That
file says whether the repository uses GitHub or another tracker and provides
the commands for issue searches, edits, labels, assignment, relationships,
branches, and status changes. If the file is missing, stop and say that
scaffold-repository provides it.
Use /to-spec when the user needs to publish a new specification or issue.
Begin issue work with the Engineering plugin's working-on-issues skill.
Follow docs/issue-tracker.md for all other issue work, even when it selects
GitHub.
For GitHub work:
- Read the repository's root instructions and any documents that govern the
requested operation.
- Use the current directory's default
gh repository unless the repository
instructions allow work in another repository.
- Check whether the repository is public before publishing text. Do not expose
private URLs, credentials, or private paths in public pull requests or
releases.
- Use the appropriate instructions below.
- For pull request comments, read
the pull request comment instructions.
- To build, publish, and merge completed work, use the Engineering plugin's
patina-mode skill, which owns the pull request and shipping workflow.
- To create or update a pull request by hand, follow the repository's body
contract with
gh pr create --body-file. Honor its draft, check, and review
rules.
- For checks, releases, repository settings, and other GitHub data, use
gh
after reading the repository instructions.
Use the pull request body headings named by the repository instructions in
their existing order. Follow the commit and pull request title rules in the
repository's AGENTS.md.
1---2name: using-github-23description: Work with repository settings, pull requests, reviews, checks, and releases on GitHub. Use for GitHub operations other than issue tracking.4---56# Using GitHub78Read `docs/issue-tracker.md` at the repository root before any issue work. That9file says whether the repository uses GitHub or another tracker and provides10the commands for issue searches, edits, labels, assignment, relationships,11branches, and status changes. If the file is missing, stop and say that12`scaffold-repository` provides it.1314Use `/to-spec` when the user needs to publish a new specification or issue.15Begin issue work with the Engineering plugin's `working-on-issues` skill.16Follow `docs/issue-tracker.md` for all other issue work, even when it selects17GitHub.1819For GitHub work:20211. Read the repository's root instructions and any documents that govern the22 requested operation.232. Use the current directory's default `gh` repository unless the repository24 instructions allow work in another repository.253. Check whether the repository is public before publishing text. Do not expose26 private URLs, credentials, or private paths in public pull requests or27 releases.284. Use the appropriate instructions below.2930- For pull request comments, read31 [the pull request comment instructions](workflows/pr-comments.md).32- To build, publish, and merge completed work, use the Engineering plugin's33 `patina-mode` skill, which owns the pull request and shipping workflow.34- To create or update a pull request by hand, follow the repository's body35 contract with `gh pr create --body-file`. Honor its draft, check, and review36 rules.37- For checks, releases, repository settings, and other GitHub data, use `gh`38 after reading the repository instructions.3940Use the pull request body headings named by the repository instructions in41their existing order. Follow the commit and pull request title rules in the42repository's `AGENTS.md`.