skills.rest
flexigpt
flexigptOFFICIAL
Explore all skills by this author →
GitHub

reviewing-code

Audit code, diffs, PRs, and APIs for defects and security risks.

4|1|Updated Jul 23, 2024
Search Tags:#security#bugs#code#code-review#audits#reviewing#merge-safety
One-click install
npx skills add https://github.com/flexigpt/flexigpt-app --skill reviewing-code-flexigpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/flexigpt/flexigpt-app/tree/main/internal/builtin/skills/software-dev/reviewing-code
Command: npx skills add https://github.com/flexigpt/flexigpt-app --skill reviewing-code-flexigpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing codebases, diffs, PRs, modules, and API/config surfaces to identify defects, security risks, reliability issues, and maintainability hazards, enabling safer merges and higher-quality software.

Core Features & Use Cases

  • Code review for bugs, security flaws, performance risks, and interface safety across changes and branches.
  • Diff and PR assessment to verify fixes and audit merge safety.
  • Use Case: When validating a patch, run an in-depth review to surface critical risks and recommended mitigations for developers and reviewers.

Quick Start

Analyze the specified code changes by summarizing top findings and suggested mitigations for the current PR.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I review a pull request for security risks and bugs?▼

Reviewing a pull request for security risks and bugs involves auditing the diff to identify defects, reliability issues, and maintainability hazards, producing formal findings with risk scoring and evidence-based conclusions for safer merges.

What is the best way to check merge safety before integrating code changes?▼

The best way to check merge safety is by assessing code changes and diffs to surface critical defects, security flaws, and performance risks, generating recommended mitigations and evidence-based conclusions to validate safe integration across modules.

How do I verify that a code patch actually fixes the intended reliability issue?▼

Verifying a code patch fixes a reliability issue requires running a fix-verification review that audits the updated code to confirm the resolution, evaluates interface safety, and generates formal findings with risk scoring to ensure no new hazards are introduced.

Can I audit API and configuration interfaces for safe usage across modules?▼

You can audit API and configuration interfaces for safe usage across modules using interface-review mode, which assesses code surfaces for defects, security risks, and maintainability hazards to ensure safe interactions.

What types of code review modes are available for assessing code slices and changes?▼

Available code review modes for assessing code slices and changes include change-review, code-slice-review, interface-review, and fix-verification, each applying formal findings and risk scoring to target specific defect and security analysis scenarios.

Related Skills

Explore More Software Engineering Skills→
5unnykum4r5unnykum4r
10

Code Review

Review source code for security, correctness, performance, and maintainability issues.

Community
Intermediate
zm2231zm2231

code-refactoring

Refactor code to improve quality, readability, and maintainability.

Community
Advanced
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
projectedanxprojectedanx
1

requesting-code-review

Automate pre-commit code verification with security analysis, linting, and subagent review.

Community
Advanced