repo-maintain

Audit and remediate repository standards across multiple projects with JSON reports.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tsilva/claude-skills --skill repo-maintain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-maintain
Source: https://github.com/tsilva/claude-skills/tree/main/plugins/repo-maintain/skills/repo-maintain
Command: npx skills add https://github.com/tsilva/claude-skills --skill repo-maintain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

Audits and remediates repositories to enforce consistent README, branding, licensing, and configuration across a workspace.

Core Features & Use Cases

  • Comprehensive repo health checks: readme existence, license visibility, logo presence, .gitignore completeness, CLAUDE settings, and dependency configuration.
  • Automated remediation through safe fixes: license insertion, logo generation, claude settings, and dependabot setup via built-in scripts.
  • Operational workflow: run audits across multiple repos and generate JSON reports for downstream remediation steps.

Quick Start

Use the repo-maintain skill to audit all repositories in the current directory: uv run {SKILL_DIR}/scripts/audit.py --repos-dir .

Frequently Asked Questions about repo-maintain

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

FAQPage Schema
How do I audit multiple repositories for standardization and compliance?

You can audit multiple repositories for standardization by running the embedded Python script across a target directory to check README existence, license visibility, logo presence, .gitignore completeness, and dependency configuration, generating a structured JSON report for remediation.

What does repository standardization enforcement cover for multi-repo maintenance?

Repository standardization enforcement covers repo metadata, logo presence, license and gitignore compliance, CLAUDE settings, and dependency management across diverse projects, applying deterministic checks to ensure consistent branding and configuration.

How do I set up Dependabot and license files across multiple repositories?

You can set up Dependabot and insert license files across multiple repositories using the skill's automated remediation scripts, which safely apply fixes like license insertion and Dependabot configuration based on the generated audit report.

Do I need git and gh installed to audit and remediate repositories?

Yes, you need both git and gh installed as dependencies to audit and remediate repositories, as the skill relies on these tools to access repository metadata and enforce standardized configuration across your workspace.

What's the best way to generate a JSON audit report for repository remediation steps?

The best way to generate a JSON audit report for repository remediation is running the built-in audit script with the target repositories directory, which performs deterministic checks and emits a structured report for downstream remediation workflows.

Why are my repository health checks failing for README and branding compliance?

Repository health checks fail for README and branding compliance when audits detect missing or inconsistent files, which the remediation scripts address by generating logos, inserting licenses, and applying standardized configuration across repositories.