skills.rest
quantfiction
quantfictionCOMMUNITY
Explore all skills by this author →
GitHub

review

Identify and document code quality, bug, test, and documentation issues in current changes.

Updated Aug 27, 2026
Search Tags:#git#documentation#quality#review#bugs#code-review
One-click install
npx skills add https://github.com/quantfiction/dotfiles --skill review-quantfiction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/quantfiction/dotfiles/tree/main/claude/plugins/global-skills/skills/review
Command: npx skills add https://github.com/quantfiction/dotfiles --skill review-quantfiction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly identify and document issues in proposed changes, covering code quality, bugs, tests, and documentation gaps to improve merge readiness.

Core Features & Use Cases

  • Structured code-review feedback across quality, stability, tests, and docs
  • Actionable findings with severity levels and suggested fixes
  • Suitable for PRs, feature branches, or any staged/unstaged changes awaiting review

Quick Start

Review the current branch or staged changes and provide an actionable feedback summary.

Frequently Asked Questions about review

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

FAQPage Schema
How do I get structured code-review feedback for git staged changes?▼

Structured code-review feedback for git staged changes is generated by identifying and documenting issues across code quality, bugs, tests, and documentation, yielding location-specific findings with severities and actionable fixes to improve merge readiness.

What does a formal code-review checklist cover for open PRs?▼

A formal code-review checklist for open PRs covers code quality, stability, tests, and documentation gaps, enforcing a structured review process that outputs actionable recommendations and location-specific findings for proposed changes.

Can I review unstaged changes on a feature branch before merging?▼

You can review unstaged changes on a feature branch before merging. The process applies to staged, unstaged, and open PR changes, enabling structured feedback across quality, reliability, and documentation to document issues fast.

What's the best way to document bugs and code quality issues in current changes?▼

The best way to document bugs and code quality issues in current changes is using a formal review checklist that outputs structured recommendations, identifying issues across quality, reliability, and documentation with specific severities and suggested fixes.

Does the code review output include severity levels for identified bugs?▼

The code review output includes severity levels for identified bugs. It enforces a formal checklist to yield actionable findings, providing structured recommendations with severity levels and suggested fixes for code quality and documentation gaps.

Related Skills

Explore More Software Engineering Skills→
jie-mengjie-meng
1

code-review-staged

Review staged git changes and generate a six-section code review with a commit message.

Community
Advanced
kurokeitakurokeita
1

find-bugs

Analyze code changes to identify bugs, security vulnerabilities, and quality issues.

Community
Intermediate
TopengDevTopengDev

preflight

Run local linting, testing, and building checks before pushing code.

Community
Advanced
VXerysVXerys

caveman-review

Generate concise code review comments with severity levels for pull requests.

Community
Basic