// Use when drafting pull-request titles, descriptions, change summaries, risk notes, validation sections, or reviewer handoff text; do not use for implementation design, release publishing checks, or raw test failure triage.
Use when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence, or workflow readiness checks.
Supports preparing commits, pre-commit hooks, Spotless, formatting or linting, validation before commit, staging files, and writing conventional commits.
Use for GitHub issue triage and local investigation, including gh issue workflows, picking a fresh issue, reproducing issue reports, and planning regression coverage.
Use for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and validation recommendations.
Use when running, selecting, authoring, or triaging integration tests, Kotest specs, Gradle matrix tasks, FakePlayer-backed test cases, or compact test-result files; do not use for unrelated production-only edits, release publishing, or general PR prose.
Use for Java 8 backports, Bukkit/Paper version differences, NMS/reflection, PacketEvents compatibility, fake-player implementation choices, and feature-detection design; do not use for release publishing, PR wording, or simple test-running decisions.
| name | pr-draft-summary |
| description | Use when drafting pull-request titles, descriptions, change summaries, risk notes, validation sections, or reviewer handoff text; do not use for implementation design, release publishing checks, or raw test failure triage. |
Use this skill to turn completed work into reviewer-facing prose. Keep wording concise, accurate, and in British English.
release-readiness-review for release checks.integration-test-verification.## Summary
-
-
## Validation
-
## Risks / notes
-
When asked for a commit message, use conventional commits format, for example:
docs: add repo-local agent skill guidance
## Summary
- Added repo-local agent skills for integration-test verification, compatibility strategy, module config changes, release readiness, and PR summaries.
- Slimmed root `AGENTS.md` to always-on rules plus routing guidance, with historical details relocated into skill references.
## Validation
- Checked skill frontmatter and folder-name matches.
- Confirmed no plugin runtime files changed.
## Risks / notes
- opencode must be restarted before new or changed skills are available in a running session.