antigaslighter

Analyze GitHub Actions logs and state files to verify true workflow outcomes.

13|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/kody-w/rappterbook --skill antigaslighter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antigaslighter
Source: https://github.com/kody-w/rappterbook/tree/main/.claude/skills/antigaslighter
Command: npx skills add https://github.com/kody-w/rappterbook --skill antigaslighter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that workflows, deployments, and scripts actually did what they claimed, surfacing silent failures, state drift, and non-contributory runs.

Core Features & Use Cases

  • Detects silent failures by evaluating evidence beyond exit codes.
  • Audits key state files, logs, and artifacts to identify drift and unreported results.
  • Applies to CI/CD pipelines, deployments, and automation tasks to improve trust and accountability.

Quick Start

Initiate an audit to verify that workflows and scripts produced tangible results and flag any silent failures.

Frequently Asked Questions about antigaslighter

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

FAQPage Schema
How do I detect silent failures in GitHub Actions CI pipelines?

Surface silent failures by inspecting GitHub Actions logs, state files, and posted artifacts to verify tangible outcomes rather than trusting exit codes. This catches unreported errors and state drift that pipelines miss.

What is evidence-based workflow verification and when do I need it?

Evidence-based workflow verification determines true success by inspecting artifacts, logs, and state files instead of exit codes. It is needed for CI/CD pipelines, deployments, and audit trails where scripts may report false successes or non-contributory runs.

How do I audit state files and artifacts to identify drift?

Audit state files and artifacts to identify drift by evaluating evidence under the state/ directory and posted deployment outputs. This process enforces accountability by confirming that scripts and workflows actually achieved their stated outcomes.

Can I verify deployment outcomes beyond exit codes for automation scripts?

Yes, you can verify deployment outcomes beyond exit codes by auditing state files, logs, and posted artifacts. This detects drift and non-contributory runs, ensuring automation tasks produce tangible results rather than false successes.

Why does my deployment script report success but the state file shows drift?

Deployment scripts report false successes when state files under state/ drift from expected conditions. Auditing these state files alongside posted artifacts and logs identifies the unreported results and mismatched state causing the silent failure.