# Software Code Review

Evaluate source code for correctness, quality, security, style conformance, and...

- Repository: https://github.com/stencila/stencila (914 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add stencila/stencila --skill software-code-review -g -a claude-code -y`
Codex: `npx skills add stencila/stencila --skill software-code-review -g -a codex -y`
Cursor: `npx skills add stencila/stencila --skill software-code-review -g -a cursor -y`
Gemini CLI: `npx skills add stencila/stencila --skill software-code-review -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add stencila/stencila`

## Description

Evaluate source code for correctness, quality, security, style conformance, and maintainability, producing a structured review report with findings and recommendations. Use when the user wants to review, critique, audit, evaluate, or inspect source code, checking for bugs, logic errors, unhandled error paths, security vulnerabilities, naming and readability issues, complexity, duplication, coupling, testability, and API design. Discovers codebase conventions independently and produces an actionable report with severity-graded findings grouped by category, prioritized recommendations, and open questions.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Overview

Review source code for correctness, quality, security, style conformance, and maintainability. This skill reads and evaluates code, it does not modify any files. The output is a structured review report with an overall assessment, strengths, severity-graded findings grouped by category, prioritized recommendations, and open questions.

Do not use this skill when the main task is to write code, refactor code, create tests, review tests, review a design, or review a delivery plan.

## Required Inputs

| Input               | Required | Description                                                          |
|---------------------|----------|----------------------------------------------------------------------|
| Target files        | Yes      | Paths to the source code files to review                             |
| Review focus        | No       | Specific areas to prioritize (e.g., "security", "error handling", "API design") |
| Target packages     | No       | Packages, crates, modules, or directories involved                   |
| Acceptance criteria | No       | Requirements or criteria the code should satisfy                     |

When used standalone, these inputs come from the user or the agent's prompt. When used within a workflow, the workflow's stage prompt will specify how to obtain them.

## Outputs

| Output          | Description                                                                   |
|-----------------|-------------------------------------------------------------------------------|
| Overall verdict | Summary assessment of the code's quality and readiness                        |
| Review report   | Structured report with strengths, findings, recommendations, and open questions |

## Steps

### 1. Gather inputs and context

Ensure the required inputs are available:

The rest: https://github.com/stencila/stencila/blob/HEAD/.stencila/skills/software-code-review/SKILL.md