Install
$ agentstack add skill-maragudk-skills-address-code-review ✓ 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.
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
Address Code Review
Work through code review comments with the user, one comment at a time. Never present multiple comments at once.
Input sources
Comments may come from:
- GitHub PR - Fetch inline and general comments using
gh api - Document in the repo - Parse whatever markdown structure is found
- Conversation - Comments given directly by the user
Process
1. Collect feedback
- GitHub PR: Use GraphQL to fetch all comments in one go. Fetch inline review comments via
pullRequest.reviewThreadsand general PR comments viapullRequest.comments. Skip already-resolved threads (isResolved). Still present outdated but unresolved comments (isOutdated), noting to the user that the code has changed since the comment was left. - Document: Read the file and extract review items.
- Conversation: Use the comments as provided.
2. Triage one at a time
For each comment, strictly one at a time:
- Present the comment to the user.
- Share your own assessment: agree, disagree, or propose an alternative. Explain your reasoning briefly.
- Wait for the user to decide what to do (apply, skip, modify, etc.).
- Record the agreed-upon action. Do not apply code changes yet.
For GitHub PR inline comments: immediately reply to the comment on GitHub and resolve the thread after discussion.
3. Apply changes
After all comments have been discussed, apply all agreed-upon code changes in one batch.
For GitHub PR general comments (which may contain multiple issues in one comment): post a single summary reply after all issues in that comment are addressed.
For document sources: update the document with status/progress as appropriate.
GitHub CLI reference
| Action | Command | |---|---| | Fetch all comments | GraphQL query on pullRequest.reviewThreads (inline) and pullRequest.comments (general) | | Reply to inline comment | gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies -X POST -f body="..." | | Reply to general comment | gh api repos/{owner}/{repo}/issues/{pr}/comments -X POST -f body="..." | | Resolve a thread | GraphQL mutation resolveReviewThread(input: {threadId: "..."}) |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: maragudk
- Source: maragudk/skills
- 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.