fxa-check-smells

Detect code smells in files changed on the current branch against main.

683|238|Updated Jun 3, 2015
One-click install
npx skills add https://github.com/mozilla/fxa --skill fxa-check-smells
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fxa-check-smells
Source: https://github.com/mozilla/fxa/tree/main/.claude/skills/fxa-check-smells
Command: npx skills add https://github.com/mozilla/fxa --skill fxa-check-smells

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews changed code for code smells across design, implementation, tests, and dependencies. Reports findings with severity and concrete fix recommendations. Operates on files changed vs main.

Core Features & Use Cases

  • Detect design, implementation, test, and dependency smells in changed files.
  • Produce severity-rated findings with actionable recommendations.
  • Use during pull request reviews to improve software quality on new changes.

Quick Start

Review the current branch diff against main and generate a prioritized list of code smells with concrete fix recommendations.

Frequently Asked Questions about fxa-check-smells

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

FAQPage Schema
How do I detect code smells in a git diff before a pull request?

Static analysis for code smells identifies maintainability issues across design, implementation, tests, and dependencies. This Skill reviews the git diff of changed files against main to report severity levels and concrete fix recommendations.

What is static analysis for code smells and when do I need it?

Static analysis for code smells detects maintainability issues across design, implementation, tests, and dependencies. You need it during pull request reviews to improve software quality by generating severity-rated findings with concrete fix recommendations.

How do I analyze a branch diff against main for maintainability issues?

Analyzing a branch diff for maintainability issues requires parsing changed files and identifying code smells. This Skill processes the git diff main...HEAD output to locate design, implementation, test, and dependency issues with actionable recommendations.

Can I get severity-rated findings for code smells in changed files?

You can get severity-rated findings for code smells by parsing the changed files in your branch diff. This Skill analyzes all touched files and produces a structured summary including issue names, locations, descriptions, and recommended fixes.

What is the best way to spot code smells across new code changes?

The best way to spot code smells across new changes is running diff analysis on the current branch. This Skill evaluates all touched files to detect maintainability issues and provides concrete recommendations for software quality improvement.