skills.rest
LPDigital-Agent
LPDigital-AgentOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-review

Review code across tech stacks and generate severity-based findings reports.

Updated Aug 23, 2026
Search Tags:#performance#security#quality-assurance#code-review#software-engineering#pull-requests
One-click install
npx skills add https://github.com/LPDigital-Agent/galderma-demo-trackwise --skill code-review-lpdigital-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/LPDigital-Agent/galderma-demo-trackwise/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/LPDigital-Agent/galderma-demo-trackwise --skill code-review-lpdigital-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables engineers to perform thorough code reviews focused on quality, maintainability, security, and performance, delivering structured findings and actionable recommendations.

Core Features & Use Cases

  • Eight-pillar evaluation (functionality, readability, security, performance, error handling, testing, standards, architecture) for every code change.
  • Structured findings with severity levels and targeted, actionable recommendations.
  • Suitable for reviewing pull requests, new implementations, or entire modules to improve quality before merge.

Quick Start

Run a code review on a target PR or file 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
What is the best way to structure code review findings before a merge?▼

The best way to structure code review findings is by using severity levels and targeted recommendations for each issue, ensuring maintainability and quality-assurance issues are clearly communicated to guide fixes before merging.

Can I use this code review process for any tech stack and entire modules?▼

Yes, you can use this code review process across any tech stack to evaluate new implementations or entire modules, applying the same eight-pillar evaluation to identify issues in functionality, architecture, and performance.

What are the eight pillars of code review?▼

The eight pillars of code review are functionality, readability, security, performance, error handling, testing, standards, and architecture, which together ensure comprehensive quality-assurance and maintainability for software-engineering changes.

When do I need a structured code review report?▼

You need a structured code review report when evaluating pull requests or new implementations to ensure quality before a merge, as it captures severity-based findings and actionable recommendations to guide necessary fixes.

Related Skills

Explore More Software Engineering Skills→
Parthivjoshi29Parthivjoshi29

reviewing-code

Evaluate code for bugs, security vulnerabilities, and quality issues with structured feedback.

Community
Advanced
ChimeraFoundationaChimeraFoundationa

code-review

Review code changes for security, reliability, and readability issues.

Community
Intermediate
zli5460zli5460
2

github-code-review

Review GitHub pull requests and local code changes with inline comments.

Community
Advanced
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic