assurance-status

Verify repository assurance documentation presence and analyze drift and coverage issues.

5|Updated Mar 4, 2026

Search Tags:#monitoring #compliance #repository #status #drift #assurance

Ready to run

npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill assurance-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: assurance-status
Source: https://github.com/nicholls-inc/claude-code-marketplace/tree/main/crosscheck/skills/assurance-status
Command: npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill assurance-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides an automatic, up-to-date status overview of a repository's compliance with an established assurance hierarchy, helping teams quickly identify gaps and drift.

Core Features & Use Cases

Automated Onboarding Check: Verifies the presence of essential assurance documentation and rules in the repository.
Status Dashboard Reporting: Summarizes the current state of assurance documents, invariant coverage, protected surface edits, and FP tracker metrics.
Use Case: A team can run this skill regularly to monitor their compliance status, detect any missing documentation, and identify drift in project assurance levels.

Quick Start

Run the assurance-status skill on your project to generate a concise health report and identify compliance gaps.

Frequently Asked Questions about assurance-status

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

FAQPage Schema

How do I monitor repository compliance with an assurance hierarchy?▼

Repository compliance monitoring is done by verifying documentation presence and analyzing drift and coverage issues. This skill evaluates repo files, CI logs, and coverage data to flag deviations from formal assurance frameworks.

What is assurance drift detection in a software repository?▼

Assurance drift detection identifies deviations from established compliance frameworks by analyzing coverage data and documentation gaps. It helps teams quickly flag missing rules and track declining project assurance levels over time.

How do I generate a status dashboard for project assurance documents?▼

Generate a status dashboard by running an automated check that summarizes assurance documents, invariant coverage, and protected surface edits. It produces a concise health report highlighting compliance gaps and missing documentation.

Do I need CI logs and coverage data to verify repository assurance compliance?▼

Yes, verifying repository assurance compliance requires access to repo files, CI logs, and coverage data to accurately evaluate the current state. These inputs are needed to detect drift and analyze invariant coverage issues.

What's the best way to automate onboarding checks for assurance documentation?▼

Automate onboarding checks by verifying the presence of essential assurance documentation and rules in the repository. This approach provides an up-to-date status overview, helping teams quickly identify missing compliance files.