fz-code-reviewer

Flag high-priority code-review issues in unstaged git diff changes.

1|Updated Jun 7, 2024

Search Tags:#risk-assessment #static-analysis #quality-assurance #code-review #pull-request #review-patterns

Ready to run

npx skills add https://github.com/jsco2t/dotfiles --skill fz-code-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fz-code-reviewer
Source: https://github.com/jsco2t/dotfiles/tree/main/.claude/skills/fz-code-reviewer
Command: npx skills add https://github.com/jsco2t/dotfiles --skill fz-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flag and prioritize code-review issues in PR changes according to DevI and DevC patterns, reducing noise and surfacing high-signal feedback.

Core Features & Use Cases

Confidence-based filtering: reports only high-priority items that matter in PR reviews.
Scope-aware review: by default reviews unstaged changes from git diff, with optional per-file or scope adjustments.
Clear reviewer guidance: aligns feedback with DevI and DevC review styles and terminology.

Quick Start

Review the current unstaged changes with git diff and return a concise, high-priority issue report in DevI/DevC style.

Frequently Asked Questions about fz-code-reviewer

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

FAQPage Schema

How do I review unstaged git diff changes for high-priority pull request issues?▼

Reviewing unstaged git diff changes for pull request issues involves analyzing code against DevI and DevC patterns to flag backward compatibility, concurrency safety, and logging quality problems. This yields concise, high-signal reviewer feedback.

What is static analysis for code review and how does confidence-based filtering work?▼

Static analysis for code review identifies risks by scanning git diff outputs. Confidence-based filtering works by suppressing low-priority noise and reporting only high-priority, actionable items that matter in pull request reviews.

How do I check naming consistency and dead-code elimination in my current PR changes?▼

To check naming consistency and dead-code elimination in PR changes, apply DevI and DevC review patterns to the unstaged git diff. This enforces production-grade criteria and generates actionable guidance for robust code.

Can I scope static analysis to specific files instead of the entire git diff?▼

Yes, you can scope static analysis to specific files instead of the entire git diff. The review scope is adjustable per-file, allowing targeted risk-assurance and quality-assurance checks on unstaged changes.

What's the best way to ensure backward compatibility and concurrency safety in code reviews?▼

The best way to ensure backward compatibility and concurrency safety in code reviews is enforcing DevI and DevC patterns on unstaged git diff changes. This surfaces high-priority issues with clear, actionable reviewer guidance.

Why does my static analysis report low-priority noise instead of actionable code review issues?▼

Static analysis reports low-priority noise when not applying confidence-based filtering. By reviewing unstaged git diff changes with DevI and DevC patterns, only high-priority, actionable code review issues are surfaced.