Review Implementing
Process and implement code review feedback systematically. Use when receiving review comments or FAIL verdicts and needing to address them.
Install
$ agentstack add skill-omnigentx-jarvis-review-implementing ✓ 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-omnigentx-jarvis-review-implementing) 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
Implementing Review Feedback
Adapted from mhattingpete/claude-skills-marketplace.
When to Use
- After receiving a FAIL verdict in a meeting
- When reviewer lists issues to address
- When code review comments need to be implemented
Systematic Workflow
1. Parse Feedback
- Extract individual issues from the review
- Categorize: Critical → Important → Minor
- Clarify ambiguous items before starting
2. Prioritize
Fix in order:
- Critical — Must fix before anything else
- Important — Fix before requesting re-review
- Minor — Fix if time permits, or note for later
3. Fix Each Issue
For each item:
- Locate the relevant code
- Understand the reviewer's intent
- Make the change — minimal, focused fix
- Verify — check syntax, run relevant tests
- Report — show what you changed in your
speak()
4. Request Re-Review
After fixing Critical and Important issues:
- Summarize what you fixed
- Show test results
- Ask reviewer to re-check
Handling Edge Cases
Conflicting feedback:
- Ask PM for guidance in the meeting
Breaking changes required:
- Notify team before implementing
Tests fail after fix:
- Fix tests before reporting done
Can't reproduce the issue:
- Ask reviewer for more details
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: omnigentx
- Source: omnigentx/jarvis
- 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.