Review Pr
Review a pull request using specialized reviewer agents
Install
$ agentstack add skill-jartan-llc-grimoire-review-pr ✓ 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-jartan-llc-grimoire-review-pr) 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
Review PR
Review a pull request with category-based reviewer agents.
Process
1. Get PR Context
Determine the PR number from the user's request, which may carry context beyond the number. Fetch the PR details and diff:
gh pr view
gh pr diff 2. Categorize and Review
Launch relevant reviewer agents based on changed files:
- Backend changes ->
backend-reviewer - Frontend changes ->
frontend-reviewer - Documentation changes, or code that changes public behavior ->
doc-reviewer - CI/test changes ->
test-reviewer - Non-trivial code changes ->
structure-reviewer - All changes ->
general-reviewer
3. Verify Documentation
If code changed public behavior, doc-reviewer must run -- it owns doc-code mismatch.
4. Post Review
Reviewers flag findings they could not confirm as suspected (they have no web access, and some issues resist static reading). Before posting, resolve each: verify post-cutoff versions against a live source, confirm others by re-reading the code; post anything still unresolved under Suspected as a question -- never silently dropped. Then post the review as a PR comment following review-format.md in the gitwise:github-conventions skill, ending with the reply hint -- reply with /praxis:address-review to work through findings:
gh pr comment --body ""Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jartan-LLC
- Source: Jartan-LLC/grimoire
- 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.