Pr Writing
Write concise, review-ready pull requests with clear scope, testing, and reviewer guidance
Install
$ agentstack add skill-jonathan0823-opencode-config-pr-writing ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jonathan0823-opencode-config-pr-writing) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
PR Writing Skill
What I do
- Produce clean, review-ready pull request summaries.
- Keep PRs small, focused, and easy to merge.
- Ensure communication includes context, testing, and reviewer focus areas.
- Provide reusable templates for consistent PR quality.
Workflow
1) Communicate early
- Link the related issue (or state why none exists).
- Announce ownership when starting work.
- Clarify scope before implementation.
2) Keep scope small
- Fix one problem per PR.
- Avoid bundling unrelated changes.
- Split larger work into logical commits.
3) Keep changes clean
- Follow project lint/style rules.
- Preserve existing architecture and patterns.
- Remove dead code and noisy changes.
4) Test before opening
- State what you tested (manual + automated).
- Mention environments used.
- Call out known gaps or deferred tests.
5) Write the summary for reviewers
Include:
- Related issue/context
- What changed and why
- How it was tested
- What reviewers should focus on
- Notes/risks/migrations (if any)
PR Body Template
## Related issue
- Closes #
## Summary
-
-
-
## Scope
- In scope:
- Out of scope:
## Testing
- [ ] Unit tests
- [ ] Integration tests
- [ ] Manual verification
### Test details
- Commands run:
- ``
- Results:
- ``
## Reviewer focus
- Please review:
- Risk areas:
## Notes
- Migrations/config changes:
- Follow-ups: Quick Quality Checklist
- [ ] Single clear purpose
- [ ] Minimal diff / no unrelated edits
- [ ] Clear commit history
- [ ] Tests described and reproducible
- [ ] Reviewer guidance included
- [ ] Backward compatibility considered
When to use me
Use this skill when opening a pull request or when improving an existing PR description for faster, higher-quality review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jonathan0823
- Source: Jonathan0823/opencode-config
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.