argus

Verify implementation quality against QA requests and enforce evidence tracing.

25|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/toongri/oh-my-toong-playground --skill argus-toongri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argus
Source: https://github.com/toongri/oh-my-toong-playground/tree/main/skills/qa
Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill argus-toongri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents faulty implementations from being accepted by enforcing a structured QA verification process that matches specs, checks evidence, and ensures no hidden issues slip through.

Core Features & Use Cases

  • Composable Trigger Awareness: Maps QA requests to automated checks, spec validation, QA scenarios, and user-facing hands-on verification so every required layer runs without guesswork.
  • Evidence Discipline: Guides auditors to use changed-file scopes, commands, and explicit paths for every command output, creating a reliable audit trail.
  • Use Case: When a junior engineer finishes a feature, Argus reviews the QA request, confirms changed files against the spec, runs automated checks, and documents every command output before approving the work.

Quick Start

Ask Argus to inspect the QA request, read the changed files, and confirm every trigger and evidence requirement is satisfied.

Frequently Asked Questions about argus

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

FAQPage Schema
How do I enforce spec compliance and prevent faulty code from shipping?

To enforce spec compliance and prevent shipping faulty code, use a structured QA verification process that maps code changes to automated checks, validates evidence, and flags deviations from the QA protocol before approval.

What is the best way to track evidence and audit code review changes?

Evidence tracking in code review uses changed-file scopes, executed commands, and explicit file paths for every command output, creating a reliable audit trail that confirms all QA verification requirements are satisfied.

How do I set up automated checks for QA scenarios and spec validation?

Automated checks for QA scenarios are set up by mapping composable verification triggers to specific code changes, scheduling hands-on spec validation, and enforcing evidence tracing across the affected files.

Does this QA workflow require specific dependencies to run automated checks?

No external dependencies are required to run this QA workflow, as it operates independently to detect required verification layers, schedule automated checks, and enforce evidence tracing across the listed files.

When should I use an automated QA protocol instead of manual code review?

An automated QA protocol should be used when code changes require composable verification triggers, spec compliance review, and strict evidence tracking to ensure no hidden implementation issues slip through.

Why does my code review process miss hidden implementation deviations?

Code review processes miss hidden deviations when they lack structured QA verification that enforces evidence discipline, maps triggers to automated checks, and explicitly validates changed files against the original specification.