# Review Code Against Current Standards

Code reviews can miss outdated dependencies, changed documentation, and project-specific rules. This skill guides Claude, Codex, and Claude Code through a deeper review with current ecosystem checks.

## Install

```bash
npx skillstore add arcadeai/quality-reviewer
```

## Metadata

- - Slug: arcadeai-quality-reviewer
- - Version: 1.0.0
- - Author: ArcadeAI
- - GitHub username: ArcadeAI
- - License: MIT
- - Repository: https://github.com/ArcadeAI/dexa/tree/main/.claude/skills/safeword-quality-reviewer
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, filesystem, network
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/arcadeai-quality-reviewer
- - Manifest: https://skillstore.pages.dev/api/skills/arcadeai-quality-reviewer/manifest

## Capabilities

- Reviews recent code changes for correctness, edge cases, and error handling.
- Checks local project standards such as CLAUDE.md, SAFEWORD.md, and architecture notes.
- Evaluates whether new dependencies and abstractions are justified.
- Verifies library versions and known security concerns through web research.
- Compares implementation patterns against current official documentation.
- Produces a concise verdict with critical issues and suggested improvements.

## Use Cases

- Pre-merge Pull Request Review: Review changed files before merging and identify blocking correctness, security, or standards issues.
- Dependency Upgrade Check: Confirm whether a library version is current and whether the implementation follows present documentation.
- Architecture Consistency Review: Compare a proposed implementation with local architecture notes and established project patterns.

## Prompt Templates

### Basic Change Review

```
Review my recent changes for correctness, edge cases, and clear blocking issues. Keep the verdict concise.
```

### Standards Review

```
Review these changes against the project standards files and architecture notes. Identify any rule violations or pattern mismatches.
```

### Dependency and Documentation Review

```
Review this implementation against the latest official documentation and current stable versions for the libraries it uses.
```

### Full Release Readiness Review

```
Perform a full quality review covering correctness, anti-bloat, elegance, standards, dependency versions, security issues, and current documentation.
```

## Limitations

- Requires network access to verify current versions and documentation.
- Does not replace human review for business logic or product requirements.
- May need repository context to provide accurate file and line feedback.
- Broad tool access should be restricted in sensitive repositories.

## Best Practices

- Use the skill after changes are available and the relevant files can be inspected.
- Ask for latest documentation checks when dependency behavior or versions matter.
- Treat critical findings as blockers and separate them from style preferences.

## Anti Patterns

- Do not use the skill as a substitute for tests or production monitoring.
- Do not ask it to browse external docs when repository policy forbids network access.
- Do not accept broad refactor suggestions without checking release scope and ownership.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T10:15:30.769\+00:00
- - Summary: Static external-command and weak-cryptography alerts are mostly false positives from Markdown fences, inline code formatting, and words such as description. The skill is still medium risk because it grants wildcard tool access, asks the agent to inspect project files, and requires web research.

## Stats

- - Views: 207
- - Downloads: 10
- - Favorites: 0
- - Popularity score: 0