code-quality

Execute linters, type checks, and pattern inspections on software projects.

5|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/cognitedata/builder-skills --skill code-quality-cognitedata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/cognitedata/builder-skills/tree/main/skills/code-quality
Command: npx skills add https://github.com/cognitedata/builder-skills --skill code-quality-cognitedata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill assists developers and code reviewers in identifying and fixing code quality issues, reducing bugs and technical debt in software projects.

Core Features & Use Cases

  • Automated Linting and Type Checking: Runs linters and TypeScript compilers to identify issues.
  • Code Review Guidance: Analyzes pull requests for maintainability, naming, and duplication problems.
  • Use Case: Before submitting a pull request, use this Skill to automatically detect and fix code smells, style inconsistencies, and potential bugs.

Quick Start

Use the code-quality skill to review the specified file or project directory for issues, ensuring high-quality production code.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I check code quality before submitting a pull request?

To check code quality before a pull request, you can run automated linting, type checking, and pattern inspections to detect code smells, style inconsistencies, and potential bugs. This ensures your production code is clean and maintainable.

Can I use static analysis to find duplicate code and security issues?

Yes, static analysis can identify duplicate code and security considerations. By running linters and type checks, the analysis targets dependency issues and pattern inspections to reduce technical debt and ensure robust code review processes.

How do I run TypeScript type checking and linting for project maintenance?

You can run TypeScript compilers and linters to execute static type safety checks across your project directory. This process identifies maintainability issues and naming problems, providing guidance for necessary refactoring tasks.

What is the best way to automate code review for maintainability and naming conventions?

The best way to automate code review is to analyze pull requests using linters and pattern inspections. This targets maintainability, naming conventions, and duplication problems, reducing manual effort and technical debt.

Does code quality analysis work without external dependencies?

Yes, code quality analysis operates without external dependencies. It uses internal scripts and references to execute linters, type checks, and dependency analysis directly on your specified file or project directory.

Why does static analysis fail to catch all my refactoring issues?

Static analysis may miss refactoring issues if the linters and type checks are not configured for your specific coding standards. While it detects code smells and duplication, complex logic errors require manual review.