qc

Run mix format, Credo linting, and test reviews on Elixir codebases.

2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/DecoyLex/ltix --skill qc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qc
Source: https://github.com/DecoyLex/ltix/tree/main/.claude/skills/qc
Command: npx skills add https://github.com/DecoyLex/ltix --skill qc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates comprehensive quality checks on a codebase, reducing manual review time and surfacing only actionable issues.

Core Features & Use Cases

  • Formatting checks using mix format --check-formatted to ensure consistent code style.
  • Linting with Credo to enforce best practices and catch potential issues early.
  • Test review guidance that helps identify test hygiene problems and code-quality gaps, including suggested improvements.
  • CI-friendly: can be integrated into PR workflows to surface issues before merges.

Quick Start

Run all three quality checks on the current codebase and report concise results.

Frequently Asked Questions about qc

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

FAQPage Schema
How do I run automated quality checks on an Elixir codebase?

Automated quality checks on an Elixir codebase execute formatting, linting, and test reviews using mix format and Credo. This process enforces consistent code style, applies static analysis, and identifies test hygiene gaps to generate a structured report.

What does Credo static analysis check for in Elixir projects?

Credo static analysis in Elixir projects enforces best practices and catches potential code-quality issues early. It assesses test hygiene and code-quality gaps, providing suggested improvements to surface actionable issues before merges.

Can I integrate mix format and linting checks into CI workflows?

Mix format and linting checks are CI-friendly and integrate into PR workflows to surface issues before merges. They execute mix format --check-formatted and Credo within CI pipelines to enforce automated style rules and static analysis.

How do I check Elixir test hygiene and identify code-quality gaps?

Checking Elixir test hygiene involves running a defined test-review procedure alongside mix format and Credo. This identifies test hygiene problems and code-quality gaps, generating concise results with suggested improvements.

Do I need mix format and Credo installed to run codebase quality checks?

Mix format and Credo are required to run these codebase quality checks. The process depends on mix format --check-formatted for style enforcement, Credo for linting, and a defined test-review procedure to analyze tests.

Why does mix format --check-formatted fail during local development?

Mix format --check-formatted fails during local development when the codebase contains unformatted code style violations. Running the automated quality check surfaces these formatting issues alongside linting and test-hygiene problems in a structured report.