Pantheon Inspector (Argus)

Verify code implementation against story acceptance criteria and run automated quality checks.

Updated Aug 23, 2026

Search Tags:#testing #quality assurance #code review #linting #code verification #implementation check

Ready to run

npx skills add https://github.com/jschulte/pantheon --skill pantheon-inspector-argus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Pantheon Inspector (Argus)
Source: https://github.com/jschulte/pantheon/tree/main/src/skills/pantheon-inspector
Command: npx skills add https://github.com/jschulte/pantheon --skill pantheon-inspector-argus

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that implemented code accurately reflects the story's requirements and passes essential quality checks, preventing the integration of incomplete or faulty code.

Core Features & Use Cases

Task Verification: Independently checks if each task within a story has been implemented in the codebase.
Code Citation: Provides specific file and line number references for implemented tasks.
Quality Assurance: Executes automated checks like type checking, linting, building, and testing.
Severity Classification: Categorizes findings into MUST_FIX, SHOULD_FIX, and STYLE.
Use Case: After a developer implements a new feature, invoke this Skill to automatically verify that all acceptance criteria are met and that the code adheres to project standards before merging.

Quick Start

Use the Pantheon Inspector skill to verify story key '1-3' within the sprint artifacts directory '/path/to/sprint/artifacts'.

Frequently Asked Questions about Pantheon Inspector (Argus)

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

FAQPage Schema

How do I verify code implementation against story acceptance criteria?▼

Code implementation verification checks story tasks against the codebase and executes automated quality checks like type checking, linting, building, and testing before integration. It independently confirms all acceptance criteria are met.

What does automated code review and linting check for during feature integration?▼

Automated code review classifies findings into MUST_FIX, SHOULD_FIX, and STYLE severities. It validates implementation completeness and executes build and test scripts to prevent merging incomplete or faulty code.

How do I run an implementation check on a specific story key?▼

Run an implementation check by pointing the verification process to your sprint artifacts directory and specifying the story key. The inspector verifies the targeted story tasks within the codebase.

Can I get specific file and line number references for code verification findings?▼

Code verification provides specific file and line number references for implemented tasks. This allows developers to quickly locate and address categorized findings during the independent review process.

What prerequisites do I need for quality assurance code verification?▼

Quality assurance code verification requires access to the codebase, story artifacts, and execution of build and test scripts. The workflow applies to development processes requiring independent validation before integration.

When should I use an independent code review before merging?▼

Use independent code review after implementing a new feature to automatically verify all acceptance criteria are met and code adheres to project standards. This prevents integration of incomplete or faulty code.