skills.rest
rube-de
rube-deCOMMUNITY
Explore all skills by this author →
GitHub

quality

Run linting and static analysis across JS/TS, Python, Go, Rust, and Ruby projects, then create a GitHub issue.

10|2|Updated Feb 7, 2026
Search Tags:#linting#quality#complexity#duplication#static-analysis#dead-code#github-issue
One-click install
npx skills add https://github.com/rube-de/cc-skills --skill quality-rube-de
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/rube-de/cc-skills/tree/main/plugins/dlc/skills/quality
Command: npx skills add https://github.com/rube-de/cc-skills --skill quality-rube-de

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code quality checks across a codebase: linting config detection, static analysis, and dead code identification, followed by creating a structured GitHub issue.

Core Features & Use Cases

  • Detect linting configuration across languages and run the appropriate toolchain (ESLint, Ruff, golangci-lint, Clippy, cargo-clippy) to produce machine-readable results.
  • Perform complexity, duplication, and dead code analysis to surface high-risk areas and maintainable hotspots.
  • Create a GitHub issue using the project's templates to standardize reporting and triage.

Quick Start

Run an automated code-quality assessment on a repository and generate a tracked GitHub issue with the findings.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I automate code quality checks across multiple programming languages?▼

Automate code quality checks by detecting linting configurations and running the appropriate toolchain across JS/TS, Python, Go, Rust, and Ruby projects to produce machine-readable static analysis results.

How do I create a GitHub issue for static analysis findings?▼

Create a GitHub issue for static analysis findings by using DLC templates to standardize reporting and triage for linting, complexity, duplication, and dead code results generated from your codebase.

Can I detect dead code and duplication in a Rust or Go project?▼

Yes, you can detect dead code and duplication in Rust or Go projects by running static analysis toolchains like Clippy or golangci-lint to surface high-risk areas and maintainable hotspots.

What is the best way to track code complexity analysis results?▼

The best way to track code complexity analysis results is by generating machine-readable outputs from your linters and automatically creating a structured GitHub issue to report maintainable hotspots.

Do I need a specific linter installed to run static analysis on my repository?▼

You need the relevant linter for your language, such as ESLint, Ruff, golangci-lint, or Clippy. The process detects the existing linting configuration in your project to run the appropriate toolchain.

Related Skills

Explore More Software Engineering Skills→
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
Fangyi-ChenFangyi-Chen
12

tax-import

Parse tax documents into structured data for a personal tax profile.

Community
Intermediate
fallow-rsfallow-rs
111

fallow

Analyze JavaScript and TypeScript codebases for dead code, duplication, and complexity hotspots.

Official
Advanced
thejefflarsonthejefflarson
20

hotspots

Identify security hotspots in a codebase and output a prioritized report.

Community
Advanced