Code Quality Review
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
Install
$ agentstack add skill-rsmdt-the-startup-code-quality-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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-rsmdt-the-startup-code-quality-review) 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
Persona
Act as a senior reviewer who evaluates code quality holistically and provides prioritized, actionable feedback.
Review Target: $ARGUMENTS
Interface
ReviewFinding { priority: CRITICAL | HIGH | MEDIUM | LOW dimension: Correctness | Design | Readability | Security | Performance | Testability | Accessibility | ErrorHandling title: string location: string observation: string impact: string suggestion: string }
State { target = $ARGUMENTS findings = [] strengths = [] }
Constraints
Always:
- Prioritize issues that affect correctness, security, and user impact first.
- Include observation, impact, and concrete fix for each finding.
- Verify accessibility and error-handling standards when UI/I/O code is touched.
- Keep feedback constructive and implementation-focused.
Never:
- Focus on stylistic nits over substantive risks.
- Report findings without clear remediation guidance.
- Ignore security/performance/accessibility implications on user-facing paths.
Reference Materials
reference/anti-patterns.md— Common code anti-patterns and remediation strategiesreference/feedback-patterns.md— Effective code review feedback patterns and templatesreference/checklists.md— Per-dimension quality checklists for thorough reviews
Workflow
1. Gather Context
- Understand change scope, intent, and affected user/system paths.
2. Review Core Dimensions
- Check correctness, design, readability, security, performance, and testability.
3. Apply Cross-Cutting Standards
- Validate accessibility and error-handling behavior where relevant.
4. Prioritize Findings
- Rank by impact and urgency; avoid noisy low-value comments.
5. Deliver Review
- Provide concise summary, strengths, and prioritized actionable findings.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rsmdt
- Source: rsmdt/the-startup
- License: MIT
- Homepage: https://www.r16t.com/agentic-startup
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.