skills.rest
Sassy-Dog
Sassy-DogOFFICIAL
Explore all skills by this author →
WebsiteGitHub

repo-health

Scans repositories for tech-debt markers, CI health, security alerts, and release lag via shell scripts.

Updated Mar 26, 2026
Search Tags:#tech debt#security scanning#repository health#github cli#ci monitoring#flake detection#release lag
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill repo-health-sassy-dog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-health
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/repo-health
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill repo-health-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Engineering teams lack a fast, read-only way to gauge repository health before prioritizing work. This Skill runs scripted signal scans — TODO/FIXME markers, skipped tests, CI duration and flake rates, Dependabot remediation state, code scanning, secret scanning, mobile release lag, and plugin version drift — and emits parseable JSON that a prioritization pass can consume directly. ## Core Features & Use Cases - Tech-debt and test scans: Counts TODO/FIXME/HACK markers and skipped tests with directory-level hotspot aggregation, capped output, and configurable path excludes. - CI and release health: Computes median/p90 workflow duration, detects flaky runs keyed on (headSha, event) to exclude merge-queue false positives, and measures how far TestFlight builds lag behind main. - Security exposure ranked by remediation state: Reads Dependabot, code-scanning, and secret-scanning alerts via the GitHub API, ranking parked green fix PRs and validated live credentials as P0 rather than raw alert counts. - Use Case: Before a weekly planning session, ask for a repo health scan to get one line per signal with severity tiers — for example, "CI p90: 31 min (target < 25) → P1" — plus a clean line for surfaces with no findings. ## Quick Start Ask the agent to run a repo health scan on this repository and report CI duration, dependency exposure, and tech-debt hotspots with severity tiers.

Frequently Asked Questions about repo-health

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

FAQPage Schema
How do I scan a repo for TODO and FIXME markers?▼

Run the pull-tech-debt.sh script from the repo root, optionally setting SCAN_PATHS and EXCLUDE_PATHSPECS to narrow the scan. It uses git grep with PCRE word boundaries and outputs marker lists capped at 200 plus a top-20 directory hotspot ranking.

How to measure CI duration and flaky tests with GitHub CLI?▼

Run pull-ci-health.sh with WORKFLOW set to your workflow file name. It samples recent runs via gh run list and emits JSON with median and p90 durations in minutes plus flake detection keyed on head SHA and event type to exclude merge-queue false positives.

Why does the dependency scan rank by remediation state instead of alert count?▼

Alert count is a lagging indicator that only drops when a fix merges, so a fresh CVE batch with queued fixes looks identical to a year of neglect. The script ranks parked green PRs and unremediated packages as P0 instead, surfacing what is actually actionable.

Does the repo health scan modify my repository or file issues?▼

No, every scan is read-only and makes no writes. Each script emits JSON or sectioned text to stdout, and the Skill explicitly defers issue filing to the separate assess-it skill for full multi-agent audits.

What happens when one scan fails or lacks permissions?▼

Each script degrades independently: it exits with code 10 and prints a skipped reason to stderr, such as a missing gh token scope or wrong workflow name. The remaining scans continue, and the skipped surface is reported with its reason rather than aborting the whole run.

When should I use assess-it instead of repo-health?▼

Use repo-health for a fast scripted signals scan that feeds prioritization. Use assess-it when you need a full multi-agent repository audit that produces deduplicated, PR-sized GitHub Issues filed under a tracking Epic.

Related Skills

Explore More Software Engineering Skills→
wjlmrzdwjlmrzd

github-cli

Manage GitHub repositories, issues, pull requests, Actions, and releases via CLI.

Community
Advanced
Euraika-LabsEuraika-Labs
14

tech-debt

Scan source files for debt markers and generate prioritized tech debt reports.

Official
Intermediate
Community-AccessCommunity-Access
387

scanner-bridge

Integrate GitHub Accessibility Scanner CI data with agent issue tracking and audit reporting.

Official
Advanced
3horizons3horizons

security-metrics

Collect and analyze GitHub Advanced Security metrics for code scanning, secret scanning, and Dependabot alerts.

Official
Advanced