argus

Enforce three-stage verification for code changes across PRs, commits, and diffs.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill argus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argus
Source: https://github.com/jivebreaddev/skills-claude-agent/tree/main/.claude/skills/argus
Command: npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill argus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Argus acts as a guardian for code changes, ensuring project stability by validating builds, tests, and code quality after every commit or PR. It enforces a structured, deterministic post-change review process to catch regressions and enforce standards.

Core Features & Use Cases

  • Automated Stage-based verification for changes
  • Stage 2 spec-compliance checks with explicit pass/fail criteria
  • Stage 3 code-quality feedback with rich, actionable guidance
  • Scope and compliance boundaries to prevent scope creep and policy violations Use Case: You submit a PR; Argus runs Stage 1 to verify the change, flags any missing tests or policy violations, and presents a detailed verdict with recommended fixes.

Quick Start

Submit a PR and let Argus run the Stage 1 automated checks and return a detailed Stage 3 quality report.

Frequently Asked Questions about argus

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

FAQPage Schema
How do I automate post-change code review for PRs and commits?

Post-change code review governance automates a three-stage verification process for PRs and commits. It validates builds, tests, and code quality standards before approval to catch regressions and enforce project stability.

What is a stage-based verification process for code changes?

Stage-based verification enforces code quality through three sequential checks: Stage 1 runs build, test, and lint checks; Stage 2 verifies spec compliance; and Stage 3 generates rich code-quality feedback with confidence scoring.

How do I enforce spec compliance and prevent scope creep in pull requests?

Apply explicit pass/fail criteria during Stage 2 spec compliance checks. The automated review process flags policy violations and scope creep, establishing compliance boundaries to prevent unauthorized changes from being approved.

Can I fast-path trivial code changes through automated quality checks?

Yes, trivial code changes can bypass the full review cycle using a supported fast-path mechanism. This allows minor modifications to skip the standard three-stage verification process while maintaining governance standards.

How do I generate actionable feedback with confidence scoring for code reviews?

Run Stage 3 quality checks to generate actionable code review feedback. This produces a detailed verdict with recommended fixes and a confidence score, providing explicit guidance on whether the code change meets quality standards.

How does automated code review handle pre-existing issues in a diff?

Automated code review flags pre-existing issues separately during the post-change verification process. This distinguishes new regressions from older problems, ensuring the review verdict focuses on the current change's scope.