CODE_QUALITY_CHECK

Audit codebases against a quality checklist and generate a Markdown report.

22|4|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/ivfarias/ceo --skill code-quality-check-ivfarias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CODE_QUALITY_CHECK
Source: https://github.com/ivfarias/ceo/tree/main/.gemini/skills/code-quality-check
Command: npx skills add https://github.com/ivfarias/ceo --skill code-quality-check-ivfarias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Applies a structured, checklist-driven audit to codebases or directories to identify quality gaps and produce a remediation-focused Markdown report.

Core Features & Use Cases

  • Automated rule evaluation: runs through the code-quality checklist in a deterministic fashion, producing PASS/FAIL with evidence.
  • Actionable fixes: suggests concrete remediation steps aligned with the checklist guidance.
  • Deterministic outputs: outputs a well-structured Markdown report suitable for reviews, CI gates, or team onboarding.
  • Use Case: run on a project repository to surface missing tests, formatting issues, or potential security concerns, then export a report for stakeholders.

Quick Start

Run a quality audit on the target codebase and generate a Markdown report with findings and fixes.

Frequently Asked Questions about CODE_QUALITY_CHECK

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

FAQPage Schema
How do I audit code quality and generate a markdown report?

To audit code quality, you run a checklist-driven evaluation against your target codebase directory to identify quality gaps and generate a standardized markdown report with evidence and remediation fixes.

Can I use a code review checklist to find missing tests in my repository?

Yes, a code review checklist can evaluate your project repository to surface missing tests, formatting issues, and potential security concerns, then output actionable remediation steps for stakeholders.

What is the best way to automate static analysis checks for CI workflows?

Automating static analysis for CI workflows involves running deterministic code-quality rule evaluations with stop conditions against your codebase, producing PASS or FAIL evidence suitable for CI gates.

Does checklist-based code auditing work for manual QA in software projects?

Checklist-based code auditing works for manual QA by evaluating multiple files or directories against defined rules, then exporting a structured markdown report to guide team onboarding and reviews.

How do static analysis rules handle scope limits when auditing a codebase?

Static analysis rules respect meta scope boundaries when auditing a codebase, loading inputs from a target path and applying stop conditions to evaluate only the defined file or directory scope.

What are the limitations of deterministic code-quality audits?

Deterministic code-quality audits rely on predefined checklist rules and stop conditions, meaning they only evaluate configured quality dimensions and may miss context-specific issues outside the static analysis scope.