firefly-code-reviewer

Name: firefly-code-reviewer
Availability: InStock
Author: Firefly Framework

Detect reactive correctness and architectural violations in Firefly Framework projects.

Updated Aug 23, 2026

Search Tags:#static-analysis #spring-boot #code-review #cqrs #reactive #firefly-framework

Ready to run

npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill firefly-code-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are time-consuming and prone to human error. The Firefly Code Reviewer automates a comprehensive, rules-based check against Firefly conventions to validate reactive correctness, package structure, naming conventions, RFC 7807 error handling, CQRS patterns, and Spring Boot best practices.

Core Features & Use Cases

Systematic checklist-based review that surfaces BLOCKER, WARNING, and INFO violations with precise file-and-line citations.
Cross-cutting coverage: reactive correctness, project packaging, naming conventions, error handling, CQRS, and Spring Boot alignment.
Use Case: during PR review or onboarding, automatically generate a remediation plan and ensure code conforms to Firefly standards.

Quick Start

Run the code-reviewer on your Firefly module to generate a structured, standards-based review report.

Frequently Asked Questions about firefly-code-reviewer

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

FAQPage Schema

How do I automate Spring Boot code review for reactive correctness and CQRS patterns?▼

Automating a Spring Boot code review for reactive correctness applies a structured checklist to detect architectural violations, surfacing findings with severity levels and precise file paths.

What is the best way to check Firefly Framework packaging and naming conventions in a pull request?▼

Checking Firefly Framework packaging and naming conventions in a pull request requires running an automated rules-based audit. It enforces project structure standards and reports BLOCKER or WARNING violations with exact line numbers for remediation.

Does the automated code review work for Firefly Framework onboarding and codebase audits?▼

The automated code review works for Firefly Framework onboarding and codebase audits by validating code against standards. It generates a structured remediation plan that ensures new and existing code conforms to reactive and architectural rules.

How does the reviewer report RFC 7807 error handling violations?▼

The reviewer reports RFC 7807 error handling violations by citing exact file paths and line numbers. It categorizes each finding under BLOCKER, WARNING, or INFO severity levels to guide developers through the required remediation.

Can I use static analysis to enforce CQRS and reactive patterns without manual checks?▼

Using static analysis to enforce CQRS and reactive patterns eliminates manual checks by applying a comprehensive rules-based evaluation. It automatically detects correctness issues and packaging violations, returning a structured report for remediation.