code-quality

Detect and fix code-quality issues across linting, static analysis, testing, and documentation standards.

24|8|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Fujigo-Software/f5-framework-claude --skill code-quality-fujigo-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/Fujigo-Software/f5-framework-claude/tree/main/plugins/f5-core/skills/code-quality
Command: npx skills add https://github.com/Fujigo-Software/f5-framework-claude --skill code-quality-fujigo-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code quality guidance and tooling standards to ensure clean, maintainable, and secure code across teams.

Core Features & Use Cases

  • Linting and static analysis guidelines to catch issues early.
  • Documentation and naming conventions to improve readability and onboarding.
  • Workflow integration with CI/CD to enforce quality gates and consistent reviews.

Quick Start

Configure linting, testing, and documentation workflows to start enforcing code-quality standards across your project.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I enforce strict linting and static analysis rules for a TypeScript project?

To enforce strict linting and static analysis, configure automated quality gates and robust review practices within your TypeScript project to detect and fix code-quality issues early across your codebase.

What is the best way to integrate code-quality checks into a CI/CD workflow?

Integrating code-quality checks into CI/CD involves setting up automated quality gates to enforce consistent reviews, catching issues across linting, testing, and documentation standards during pipeline execution before deployment.

Can I apply these code-quality standards to both NestJS and React applications?

Yes, these code-quality standards support multiple workflows across NestJS, React, and Node projects, allowing you to apply strict lint rules and robust review practices consistently across different frameworks.

How do I set up documentation and naming conventions to improve project readability?

To improve readability and onboarding, establish documentation and naming conventions that enforce code-quality standards, making your codebase cleaner and more maintainable for development teams.

Why does code quality degrade in large teams and how do quality gates help?

Code quality degrades without consistent standards, but automated quality gates enforce strict lint rules, robust review practices, and testing requirements to ensure secure and maintainable code across teams.