
PR Description
Write and maintain pull request descriptions in this repository, including the required...
Install
npx skills add OrchestratorInc/agent-orchestrator --skill pr-description -g -a claude-code -y- Repository
- OrchestratorInc/agent-orchestrator14k
- Category
- Git and review
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 777 tokens
- Runs scripts
- No, instructions only
What it does
Write and maintain pull request descriptions in this repository, including the required change-count header, the before-and-after section, and screenshots or recordings for visible changes.
PR description
Use the section order in .github/pull_request_template.md: change-count header,
What, Why, Before / After, How, Testing, Checklist. Preserve the rest of an existing
PR description when updating it.
Change-count header
Begin every PR description with these three lines, using Markdown hard line breaks so each renders separately:
Code changes: +<added> -<deleted>
Tests: +<added> -<deleted>
Others: +<added> -<deleted>
Calculate the numbers from the net diff against the PR's actual base. For a local
branch, use git diff --numstat <base>...<head>. After pushing, prefer GitHub's
per-file additions and deletions. Recalculate after the final push rather than
summing commit churn or estimating counts.
Count every changed file exactly once:
- Code changes: handwritten implementation, including SQL, migrations, styles, and executable scripts.
- Tests: test code, fixtures, snapshots, and test-only helpers.
- Others: generated or vendored files, lockfiles, documentation, configuration, and assets. Generated output belongs here even when it contains source code.
Show +0 -0 for empty categories. Binary files have no line count; mention their
count separately when present. Add a brief qualifier when useful, such as
Others: +11 -0 (generated sqlc).
Before / After
Every PR has a ## Before / After section with a two-column table, one row per
behavior that changed:
| Before | After |
| --- | --- |
|  |  |
| `ao session ls` exits 1 when a project has no sessions | Prints `No sessions` and exits 0 |

