assertion-triage

Classifies MT-BTI assertions and flags candidates for removal based on run history.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill assertion-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assertion-triage
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/assertion-triage
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill assertion-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you classify why GT-KB assertions are failing and routes chronic, consistently failing assertions toward structured, owner-approved retirement decisions.

Core Features & Use Cases

  • Categorize failing assertions: Segregates assertion failures into genuine_drift, chronic_noise, flaky, healthy, or uncategorized using read-only analysis of assertion run history.
  • Surface retirement candidates: Generates a candidate list/report for chronic_noise assertions ready for owner review.
  • One-at-a-time owner AUQ workflow: Produces AskUserQuestion envelopes per assertion and applies only owner-approved decisions to the knowledge base in a gated way.

Quick Start

Run the categorization pass by executing the triage command on the repository state so the Skill can produce per-assertion category outputs and candidate summaries for review.

Frequently Asked Questions about assertion-triage

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

FAQPage Schema
How do I triage failing test assertions into genuine drift versus flaky noise?

Assertion triage categorizes failing test assertions into genuine_drift, chronic_noise, flaky, or healthy by performing read-only analysis of historical assertion runs to isolate consistent failures from intermittent behavior.

What is the best way to retire chronically failing specifications without breaking governance rules?

Specification retirement requires an AskUserQuestion workflow that produces owner-approved decision packets, ensuring chronically failing assertions are only mutated or retired after explicit gated approval from the specification owner.

How do I start categorizing assertion failures in my repository?

To categorize assertion failures, execute the triage command on your current repository state, which generates per-assertion category outputs and a candidate summary report for owner review.

When should I run assertion triage during the test quality lifecycle?

Assertion triage applies during quality cycles after verifying affected implementation paths and before promoting specifications to verified status, ensuring only stable assertions advance in the governance pipeline.

Does assertion triage automatically modify or delete failing specifications?

Assertion triage does not automatically modify specifications; it performs read-only inference over assertion runs and only applies changes through an explicit apply-decision packet after owner approval via the AskUserQuestion gate.

Why do some assertion failures get classified as uncategorized instead of flaky or genuine drift?

Assertion failures are classified as uncategorized when the read-only analysis of assertion run history lacks sufficient evidence to confidently assign the failure to genuine_drift, chronic_noise, flaky, or healthy categories.