Skip to content
Skills Library
Programming · Review & audit

code-reviewing

/code-reviewing

Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.

Repository
ai-config ↗
Licence
GPL-3.0
Last repository change
08.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.

Original author description

Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.

How it works

  1. Establish scope
  2. Review priorities
  3. Findings
Original SKILL.md headings · 43 lines, 228 words
SKILL.md preview
---
name: code-reviewing
description: Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.
---

# Code Review

Review the change in its repository context and report actionable findings,
not a generic style checklist.

## Establish scope

Inspect the request, applicable project guidance, working-tree state, staged
and unstaged diffs, and relevant surrounding code. Use history when it helps
explain local conventions or intent.

If the review target is ambiguous, state the assumed range or ask one focused
question. Do not mix unrelated pre-existing code into the findings without
labelling it.

## Review priorities

Use judgement based on the change's risk. Consider:

- correctness, edge cases, and error handling;
- security, privacy, trust boundaries, and secret exposure;
- compatibility, migrations, and public contracts;
- concurrency, state consistency, resource use, and performance;
- maintainability in the repository's existing idiom; and
- whether tests and other verification support the claimed behavior.

Duplication, function length, and naming are signals rather than universal
failures. Recommend refactoring only when it makes this code clearer or safer.

## Findings

Lead with findings ordered by severity. For each one include:

- the precise file and line or symbol;
- the behavior or risk;
- why it matters in a realistic scenario; and
- a concrete direction for resolution when useful.

Separate blocking defects from non-blocking suggestions. Avoid praise,
restating the diff, or speculative concerns without a plausible failure mode.
If no findings remain, say so and identify any important verification limits.

Versions

RepositoryScoreLicence
This page · aspiers/ai-config90GPL-3.0
shunwuyu/ai_lesson100MIT

Database snapshot: 13.11.2026 · package version 780a53450d97 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-review
    Review code for correctness, security, performance, and maintainability. Use when the user asks to "review this code", "check my changes", "review PR", "audit", or "what do you think of this approach".
  • 100code-review
    Reviews code changes for quality, correctness, security, and maintainability with an independent perspective. Use when the user asks to "review the code", "check my changes", "review the implementation", or mentions code review, PR review, or quality check.
  • 100code-review
    Reviews pull requests and code changes for correctness, conventions, maintainability, performance, test coverage, and security. Use when the user asks for a code review, PR review, feedback on a diff, or to check code quality.
  • 90code-review
    Review code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.
  • 100code-review-evidence
    Use when before merging a PR or after a nontrivial code change. Review a change for correctness, security, maintainability and scope fit with reproducible findings. Do not use when pure copy editing with no executable code or system behavior.
  • 100code-review
    Review C code changes for correctness, safety, and style. Use this when you want to review C code changes or PRs.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.