repo-analyze-quick

Name: repo-analyze-quick
Availability: InStock
Author: chzarles

Identify critical showstoppers in a repository with a fast health check.

1|Updated Jan 19, 2025

Search Tags:#security #audit #health #ci #tests #repo #quick

Ready to run

npx skills add https://github.com/CHZarles/dotfiles --skill repo-analyze-quick-chzarles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-analyze-quick
Source: https://github.com/CHZarles/dotfiles/tree/main/claude/skills/repo-analyze-quick
Command: npx skills add https://github.com/CHZarles/dotfiles --skill repo-analyze-quick-chzarles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify critical showstoppers in a repository so you can ship with confidence.

Core Features & Use Cases

Quick health pulse of the repository root that flags broken, dangerous, or missing critical items
Defaults to a conservative assessment (B) when no issues are detected
Produces a concise report suitable for gatekeeping in CI or manual reviews

Quick Start

Run this from the repository root to generate a fast, high-signal health snapshot.

Frequently Asked Questions about repo-analyze-quick

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

FAQPage Schema

How do I do a quick repository health check to find critical showstoppers?▼

A quick repository health check identifies critical showstoppers by scanning the repo root for broken, dangerous, or missing items. It provides a fast, high-signal pulse rather than a full audit, returning a concise summary of actionable issues.

What is a fast repo health audit and how does it work?▼

A fast repo health audit operates from the repository root to flag critical issues. It defaults to a conservative assessment when no issues are detected and produces a concise report highlighting dangerous or missing items suitable for manual reviews.

How do I use a repo health check for CI gatekeeping?▼

To use a repo health check for CI gatekeeping, run it from the repository root to generate a concise report of actionable showstoppers. This high-signal snapshot prevents merging broken or dangerous code by flagging critical missing items.

When do I need a quick repo health check instead of a full security audit?▼

You need a quick repo health check when you require a fast pulse on critical showstoppers rather than a full security audit. It highlights broken, dangerous, or entirely missing items, providing a concise summary suitable for rapid manual reviews or CI gatekeeping.

What does a conservative assessment mean in a repo health check?▼

A conservative assessment in a repo health check means the tool defaults to a B rating when no critical issues are detected. This ensures a baseline standard of repository health without triggering false positives during the fast pulse check.

Can I run a repo health check from any directory or only the repository root?▼

You must run the repo health check from the repository root. Operating from the root directory allows the tool to accurately identify critical showstoppers, dangerous configurations, or entirely missing items across the entire project structure.