code-quality

Identify code quality issues and code smells in Elixir projects using Credo.

66|9|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/www-zaq-ai/zaq --skill code-quality-www-zaq-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/www-zaq-ai/zaq/tree/main/.agents/skills/code-quality
Command: npx skills add https://github.com/www-zaq-ai/zaq --skill code-quality-www-zaq-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality code by identifying and reporting on code quality issues and code smells.

Core Features & Use Cases

  • Credo Errors: Lists errors identified by the Elixir code analysis tool Credo.
  • Code Smells: Highlights lines of code with potential issues or bad practices.
  • Workflow Integration: Designed for use within GitHub workflows for continuous code quality checks.
  • Use Case: For a developer maintaining an open-source project on GitHub, this Skill can be used to automatically identify and flag code quality issues before code merges.

Quick Start

Run the code-quality skill on your repository to automatically check for code quality issues.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I check Elixir code quality and code smells in GitHub workflows?

To identify code smells in an Elixir project, run Credo to highlight lines of code with potential issues or bad practices. This skill reports errors to maintain standards before code merges.

What do I need to run Credo code analysis on my Elixir repository?

You need Elixir and Credo installed in your environment to analyze source code. This skill leverages the Credo tool within your repository to detect quality issues.

Does this code quality skill work with standard GitHub workflow automation?

Yes, this code quality skill is designed for integration within GitHub workflows. It performs continuous code quality checks to automatically identify and flag issues before code merges.

What is the best way to enforce Elixir code standards before a pull request merge?

The best way to enforce Elixir code standards before a merge is to use Credo in GitHub workflows. This skill automatically lists identified errors and highlights code smells for developers.

Can I use this tool to identify Credo errors in open-source Elixir projects?

Yes, you can use this skill to identify Credo errors in open-source Elixir projects. It runs Credo to list errors and highlight lines of code with potential bad practices automatically.