Repository navigation
github pr closing keywords
Add a GitHub PR creation and body-update skill to the existing github-plan-wiki plugin. Require one explicit closing keyword per completed issue and preserve repository templates.
| Type | Issue |
|---|---|
| Tracking | Issue #97 |
References such as Refs #10 and grouped entries such as Close #10, #11 do not close every intended issue. The plugin has planning skills but no GitHub PR creation skill.
Add github-pull-request with template discovery, a mandatory local body validator, and post-write readback. Use standalone Fixed #number lines for completed bug issues and Close #number lines for other completed issues. Support fully qualified cross-repository references and mixed work types. Keep unfinished parent issues and reference-only issues out of closing entries. Explain that automatic closure requires a merge into the default branch; do not change the requested base or manually close issues to compensate.
Read existing PR and Issue templates on the default branch, preserve required fields and applicable metadata, and select the relevant template. Update the planning skill with Issue-template handling and a PR handoff. Update the English and Japanese README, agent skill catalog, and plugin metadata for discovery. Preserve existing authorization boundaries; this task does not create or merge a PR or push the main repository.
- Add the PR skill, body validator, and focused behavioral tests.
- Update the Issue skill template preflight and handoff, plugin discovery metadata, and English/Japanese overviews.
- Run focused tests, skill validation, marketplace validation, and an independent isolated behavioral evaluation.
Exercise multiple issues, mixed bug/non-bug targets, cross-repository targets, missing or grouped keywords, hidden examples, and reference-only work. Verify template handling and PR body readback in an isolated evaluation without live writes. Validate both changed skills and marketplace boundaries, then run git diff --check.