New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Code Review Perspectives

by macalbert in macalbert/envilder

Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

MITAuto-check passedDevelopment

Install Code Review Perspectives

skills CLI
$ npx skills add macalbert/envilder --skill code-review-perspectives -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install macalbert/envilder code-review-perspectives --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/code-review-perspectives .claude/skills/code-review-perspectives && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review-perspectives
GitHub stars
138
Token cost
~1k tokens
SKILL.md length
434 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

  • Works in 5 steps: Correctness → Architecture → Security → …
  • Tasks that involve Code review
  • SKILL.md covers When to Use, Perspectives, Severity Model and Synthesis Procedure, plus 3 more sections
  • Calls pnpm, dotnet and tsc

What it does

Code Review Perspectives is an agent skill from macalbert/envilder. Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity. Use when reviewing PRs, commits, or local changes. Includes severity model and output format.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

  • Tasks that involve Code review

Example prompts

  • “/code-review-perspectives”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Correctness
  2. Architecture
  3. Security
  4. Conventions
  5. Complexity (CRAP)

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • dotnet
    • tsc
    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Review Perspectives loads about 1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 434 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 434 words, ~1,039 tokens.

Download SKILL.mdSave it as .claude/skills/code-review-perspectives/SKILL.md (or your agent's skills folder).
name
code-review-perspectives
description
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity. Use when reviewing PRs, commits, or local changes. Includes severity model and output format.

Code Review Perspectives

Five parallel analysis perspectives for comprehensive code review. Run independently, then synthesize into a deduplicated prioritised report.

When to Use

  • Reviewing PRs or commit ranges
  • Auditing code quality before release
  • Post-implementation review
  • Any read-only code analysis task

Perspectives

1. Correctness
  • Runtime errors, logic bugs, off-by-one mistakes
  • Unhandled promises, null/undefined risks
  • Missing error propagation
  • Regressions from changed behavior
2. Architecture
  • Hexagonal architecture boundary violations (domain importing infrastructure)
  • Port/adapter misuse, DI wiring gaps
  • Command/Handler pattern violations
  • Layer dependency direction (domain → application → infrastructure)
3. Security
  • OWASP Top 10 adapted to this stack (injection, secrets exposure, SSRF)
  • Raw secret logging (must use EnvironmentVariable.maskedValue)
  • Unsafe process.env access patterns
  • Dependency-related CVE signals
4. Conventions
  • Biome style (single quotes, semicolons, 2-space indent, trailing commas)
  • Test naming: Should_<Expected>_When_<Condition>
  • AAA markers: // Arrange, // Act, // Assert: each at most once per test
  • InversifyJS decorator usage: @injectable(), @inject(TYPES.X)
  • Conventional commits in PR title
5. Complexity (CRAP)

See code-quality-crap skill for formula and thresholds.

  • Flag methods with cyclomatic complexity ≥ 4 lacking proportional coverage
  • Flag methods with complexity ≥ 6: recommend extraction

Severity Model

SeverityCriteria
CriticalSecurity, data loss, broken release, major regression
HighLikely runtime failure, incorrect business behavior
MediumCorrectness risk with limited blast radius, test gaps
LowMaintainability concern worth addressing soon
Anti-Inflation Rules
  • Not Critical unless the exact production failure is objectively demonstrable.
  • Not High unless a concrete input or state produces incorrect behavior.
  • Convention violations are Low unless they change runtime behavior.
  • Missing guards for values guaranteed by the type system are not defects.
Show full SKILL.md (186 more words)Show less

Synthesis Procedure

  1. Run all 5 perspectives (can be parallel)
  2. Merge findings, deduplicate overlaps
  3. Assign severity per the model above
  4. Order by severity descending
  5. For each finding: severity, why it matters, file:line evidence, fix direction

Output Format

Use this standalone format when the caller does not define a workflow envelope:

text
## Findings

### [Critical/High/Medium/Low]: {title}
**File:** {path}:{line}
**Why:** {explanation}
**Fix:** {direction}

## Open Questions
- {assumptions or clarifications needed}

## Summary
{1-2 sentence overview: AFTER findings, not before}

When the caller requires the canonical ReviewResult envelope from common-verification-first, place these findings under Prioritized findings, preserve the same severity and anti-inflation rules, and map the remaining sections to the corresponding envelope fields. The envelope may add orchestration routing or contract assessment; it does not redefine review semantics.

Verification

After analysis, verify findings before reporting:

  1. pnpm test: confirm test suite passes
  2. biome check && tsc --noEmit: lint compliance (no modifications)
  3. pnpm format:check: formatting (no modifications)
  4. Browser checks for website/UI changes (Playwright)
  5. Stack-specific: dotnet build/dotnet test, make check-sdk-python

Only report confirmed findings. Downgrade unverified suspicions.

Constraints

  • Only report findings for code introduced or modified in the requested diff
  • Do not report style-only nits unless they block quality gates
  • State assumptions explicitly
  • Never modify files during review: read-only analysis only

© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/code-review-perspectives of macalbert/envilder.

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Code Review Perspectives next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Review Perspectives compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Review Perspectives this skillmacalbert/envilder138—~1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Backend Code Reviewlangflow-ai/langflow156k—~3.5kAutomated safety check: NotesMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
Mole Bug Patternstw93/Mole69k—~2kAutomated safety check: PassGPL-3.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Backend Code Review

    langflow-ai/langflow

    Review backend code for quality, security, maintainability, and best practices based on established checklist rules.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Mole Bug Patterns

    tw93/Mole

    A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    69k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed

More from macalbert/envilder

All 30 skills in this repo

  • Common Architecture Decisions

    macalbert/envilder

    Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Common Git

    macalbert/envilder

    Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning.

    138 GitHub stars~991 tokensUpdated 2 days ago
    Auto-check passed

  • Common Testing Conventions

    macalbert/envilder

    Mandatory testing conventions including the narrow diagnostic exception for testing test-only code, AAA pattern, test naming, and assertions across all stacks (.NET, TypeScript, Python).

    138 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Doc Maintenance

    macalbert/envilder

    Workflow for maintaining changelogs, READMEs, and documentation files.

    138 GitHub stars~904 tokensUpdated 2 days ago
    Auto-check passed

  • Doc Sync

    macalbert/envilder

    Audit and synchronize documentation across website, READMEs, and docs/.

    138 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Dotnet Test Doubles

    macalbert/envilder

    Test doubles including Fakes (Bogus), Dummies (AutoFixture), Stubs, Spies, and Mocks (NSubstitute).

    138 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Code Review Perspectives

What does Code Review Perspectives do?

Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity. Code Review Perspectives is an agent skill from macalbert/envilder. Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity.

When should I use Code Review Perspectives?

Code Review Perspectives fits situations like: tasks that involve Code review.

How do I install Code Review Perspectives in Claude Code?

Run `npx skills add macalbert/envilder --skill code-review-perspectives -a claude-code`. Or copy the skill folder (.github/skills/code-review-perspectives in macalbert/envilder) into .claude/skills/code-review-perspectives in your project. Claude Code loads it when a task matches its description.

How do I install Code Review Perspectives in Codex?

Run `npx skills add macalbert/envilder --skill code-review-perspectives -a codex`. Or copy the skill folder (.github/skills/code-review-perspectives in macalbert/envilder) into .agents/skills/code-review-perspectives in your project. Codex loads it when a task matches its description.

Can I use Code Review Perspectives in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill code-review-perspectives -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review-perspectives, .gemini/skills/code-review-perspectives, .github/skills/code-review-perspectives and .opencode/skills/code-review-perspectives in your project.

What does Code Review Perspectives need to run?

Going by SKILL.md and its folder, Code Review Perspectives needs the command-line tools its instructions call (pnpm, dotnet, tsc and make).

Does Code Review Perspectives access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Review Perspectives safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Review Perspectives use?

Code Review Perspectives is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Review Perspectives use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Review Perspectives?

Skills that share tags, products or a category with Code Review Perspectives: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 156k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review Perspectives?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.