skills.rest
CHZarles
CHZarlesCOMMUNITY
Explore all skills by this author →
GitHub

repo-analyze-strict

Audit repository quality across structure, documentation, testing, security, and process.

1|Updated Jan 19, 2025
Search Tags:#documentation#security#auditing#governance#evidence#code-quality#repo-audit
One-click install
npx skills add https://github.com/CHZarles/dotfiles --skill repo-analyze-strict-chzarles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-analyze-strict
Source: https://github.com/CHZarles/dotfiles/tree/main/claude/skills/repo-analyze-strict
Command: npx skills add https://github.com/CHZarles/dotfiles --skill repo-analyze-strict-chzarles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a rigorous, evidence-based repository audit that flags completeness, quality, and governance gaps, starting from a strict F-grade baseline and requiring concrete evidence for every improvement.

Core Features & Use Cases

  • Conducts an exhaustive, section-by-section audit across code, tests, docs, configurations, and tooling.
  • Produces objective, evidence-backed grades, consolidated issues, and a final GO/NO-GO verdict to guide releases.
  • Generates actionable remediation guidance and a transparent audit trail suitable for governance and compliance.

Quick Start

Run this skill from the repository root to generate a rigorously documented audit that flags critical issues with concrete evidence.

Frequently Asked Questions about repo-analyze-strict

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

FAQPage Schema
How do I conduct an evidence-based repository audit for release governance?▼

An evidence-based repository audit evaluates code, tests, docs, and configs against governance principles, producing per-section grades, an issues list, and a GO/NO-GO verdict with remediation guidance.

What is a strict repo audit and how does it grade code quality?▼

A strict repo audit starts from an F-grade baseline and requires concrete evidence across structure, documentation, testing, security, and process to objectively evaluate and improve repository code quality.

How do I generate a GO or NO-GO verdict for my codebase before a release?▼

Generate a GO or NO-GO release verdict by running a comprehensive repository audit that flags completeness, quality, and governance gaps using a strict, evidence-backed grading methodology.

Can I audit repository documentation and security configurations together?▼

Yes, you can audit repository documentation and security configurations together through a section-by-section evaluation that assesses conformance with defined development principles and governance standards.

What is the best way to identify governance gaps in a software repository?▼

The best way to identify governance gaps is an exhaustive audit that reads source files, tests, configs, and docs, producing a transparent audit trail with actionable remediation guidance.

Related Skills

Explore More Software Engineering Skills→
paialexpaialex
1

project-tutorial-builder

Generate interactive onboarding tutorials from live repository state.

Community
Advanced
CHZarlesCHZarles
1

repo-analyze

Audit a repository across 15 dimensions and produce a prioritized GO/NO-GO report.

Community
Advanced
ckrono-progckrono-prog

security_scan

Conducts a multi-scanner security audit of a codebase for critical and high vulnerabilities.

Community
Intermediate
mahg-esmahg-es
3

cicd-quality

Design and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.

Official
Advanced