excusare

Name: excusare
Availability: InStock
Author: watministrator

Audit code suppression exemptions across multi-language codebases.

Updated May 20, 2026

Search Tags:#code-quality #static-analysis #risk-management #lint #overrides #exemptions

Ready to run

npx skills add https://github.com/watmin/datamancy.dev --skill excusare

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: excusare
Source: https://github.com/watmin/datamancy.dev/tree/main/excusare
Command: npx skills add https://github.com/watmin/datamancy.dev --skill excusare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weigh every exemption offered to code checkers against present truth, ensuring suppressions remain warranted as the codebase evolves.

Core Features & Use Cases

Classifies and weighs exemptions from multiple checkers (Rust, Clippy, ESLint, Python linters, and similar) to determine if they remain justified.
Tracks birth and over-time validity, surfacing whether an exemption is HOLDS, ILLEGITIMATE-AT-BIRTH, OPEN-DEFERRAL, STALE-GUARD, CLOSED-DEFERRAL, or ORPHANED.
Provides actionable remediation guidance and evidence-led rationale to keep suppressions honest across evolving codebases.

Quick Start

Run excusare on your codebase to evaluate all suppression exemptions and surface findings

Frequently Asked Questions about excusare

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

FAQPage Schema

How do I audit lint suppressions and overrides to check if they are still needed?▼

To audit lint suppressions, you evaluate every exemption against the present codebase state to determine if it remains warranted. This process classifies overrides into categories like HOLDS, STALE-GUARD, or ORPHANED to surface suppressions that should be adjusted or removed.

What is a stale lint exemption and how do I identify it in my codebase?▼

A stale lint exemption is a suppression that no longer serves its original purpose as the code evolved. You identify it by tracking the birth and over-time validity of overrides, classifying outdated suppressions as STALE-GUARD or ORPHANED for remediation.

Can I evaluate suppression overrides across multiple programming languages like Rust and Python?▼

Yes, you can evaluate suppression overrides across multi-language codebases including Rust, JavaScript/TypeScript, Python, and Java. The evaluation enforces a two-phase assessment to weigh exemptions from various linters against present truth.

When should I remove eslint disable comments or rust allow attributes from my code?▼

You should remove eslint disable comments or rust allow attributes when the exemption is classified as ILLEGITIMATE-AT-BIRTH, CLOSED-DEFERRAL, or ORPHANED. This indicates the suppression is no longer warranted by the present codebase state and should be removed.

What is the difference between an open deferral and a stale guard in code quality management?▼

In code quality management, an OPEN-DEFERRAL is a suppression tracking an actively deferred fix, whereas a STALE-GUARD is an exemption that has outlived its usefulness as the codebase evolved. Both require re-evaluation to determine if they remain warranted.