skills.rest
Appsilon
AppsilonOFFICIAL
Explore all skills by this author →
Website𝕏@appsilonGitHub

code-review

Identify and document code change issues across architecture, security, conventions, and quality.

35|9|Updated Mar 3, 2026
Search Tags:#testing#architecture#security#quality#code-review#pull-request
One-click install
npx skills add https://github.com/Appsilon/mediforce --skill code-review-appsilon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Appsilon/mediforce/tree/main/skills/code-review
Command: npx skills add https://github.com/Appsilon/mediforce --skill code-review-appsilon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code reviews are critical but time-consuming and error-prone when assessing architecture, security, coding conventions, and overall quality across PRs. This Skill helps teams standardize evaluations and catch issues earlier in the merge process.

Core Features & Use Cases

  • Systematically categorize changes by architectural layers (API, UI, data models, configs)
  • Apply a documented review checklist (referenced in references/review-checklist.md) to ensure consistency and compliance
  • Produce a structured findings report with severity levels suitable for reviewer discussions and merge decisions

Quick Start

Run the code-review tool on the current branch to generate a structured findings report

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for pull requests to catch security and architecture issues?▼

Automated code review systematically evaluates pull request diffs across architecture, security, conventions, and quality, producing a structured findings report with severity levels before merge decisions. It applies a documented checklist to ensure consistent evaluations across repositories.

What is the best way to structure pull request reviews for consistent quality checks?▼

Structured pull request reviews categorize code changes by architectural layers like API, UI, data models, and configs, applying a standardized review checklist to ensure compliance. This approach generates line-accurate findings with severity levels suitable for reviewer discussions.

Can I review specific file paths and changed components instead of an entire PR diff?▼

Yes, code review can target specific file paths and changed components across repositories rather than analyzing only the entire PR diff. This allows focused evaluation of architecture, security, and quality issues in the exact code segments being modified.

How does classifying code changes by architectural layers improve the review process?▼

Classifying code changes by architectural layers like API, UI, data models, and configs improves review focus by isolating concerns and enforcing layer-specific conventions. This structured categorization ensures reviewers assess the correct architectural context for each change.

Does automated code review require external testing dependencies to analyze pull requests?▼

No, this code review process operates independently without external dependencies, applying a built-in review checklist to analyze diffs. It systematically identifies and documents issues across architecture, security, conventions, and quality during pull request evaluations.

When should I avoid using an automated code review checklist for merge decisions?▼

Avoid relying solely on a code review checklist when addressing highly subjective architectural design debates or novel security vulnerabilities requiring human intuition, as the process systematically enforces defined workflows but may lack context for unprecedented edge cases.

Related Skills

Explore More Software Engineering Skills→
forranyforrany

verification-loop

Automate build, type check, lint, tests, security scan, and diff review for code changes.

Community
Intermediate
pextacypextacy

code-review

Identify security, quality, and maintainability issues in code changes.

Community
Advanced
xxihxxih
1

springboot-verification

Validate Spring Boot applications with build, static analysis, coverage, and security scans.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate