Pantheon Quality (Arete)

Review code files for maintainability and readability, classifying issues into MUST_FIX, SHOULD_FIX, or STYLE categories.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jschulte/pantheon --skill pantheon-quality-arete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pantheon Quality (Arete)
Source: https://github.com/jschulte/pantheon/tree/main/src/skills/pantheon-quality
Command: npx skills add https://github.com/jschulte/pantheon --skill pantheon-quality-arete

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of ensuring code adheres to high standards of quality, maintainability, and readability, preventing technical debt and improving developer productivity.

Core Features & Use Cases

  • Code Review: Automatically analyzes code for readability, maintainability, and adherence to best practices.
  • Quality Assessment: Classifies findings into MUST_FIX, SHOULD_FIX, and STYLE categories for prioritized action.
  • Use Case: Integrate this Skill into your CI/CD pipeline to automatically flag code smells and potential issues before they are merged, ensuring a consistently high code quality across the project.

Quick Start

Invoke the Pantheon Quality skill to review the files changed in the current sprint story, using the provided sprint artifacts directory.

Frequently Asked Questions about Pantheon Quality (Arete)

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

FAQPage Schema
How do I automate code review for maintainability and readability before merging?

Automating code review for maintainability involves analyzing your files to detect code smells and best practice violations. This Skill reviews specified files within a sprint artifact context, classifying issues into MUST_FIX, SHOULD_FIX, or STYLE categories to ensure high code quality before merge.

What is the best way to prioritize code smells and technical debt in a CI/CD pipeline?

Prioritizing code smells requires classifying issues by severity. This Skill outputs structured JSON findings, categorizing readability and maintainability issues into MUST_FIX, SHOULD_FIX, and STYLE buckets to help you systematically address technical debt in your pipeline.

Can I assess code quality across a specific list of files in a sprint?

You can assess code quality across specific files by invoking this Skill against a provided sprint artifacts directory. It reviews the changed files for adherence to best practices and emits structured JSON findings for quality assurance tracking.

How does automated quality assurance handle different levels of code review findings?

Automated quality assurance categorizes code review findings into three levels: MUST_FIX for critical issues, SHOULD_FIX for important improvements, and STYLE for minor readability suggestions. This structured JSON output helps developers prioritize their technical debt resolution.

Do I need specific sprint artifacts to run a maintainability check on my code?

Yes, running a maintainability check with this Skill requires a specified list of files within a given sprint artifact context. Providing the sprint artifacts directory allows the tool to accurately target and review the relevant code changes.