repomatic-audit

Audit downstream repositories against the upstream repomatic reference.

57|8|Updated Dec 9, 2021
One-click install
npx skills add https://github.com/kdeldycke/repomatic --skill repomatic-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repomatic-audit
Source: https://github.com/kdeldycke/repomatic/tree/main/.claude/skills/repomatic-audit
Command: npx skills add https://github.com/kdeldycke/repomatic --skill repomatic-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures your repository's configurations, workflows, and conventions are up-to-date and aligned with the upstream kdeldycke/repomatic reference, preventing drift and ensuring best practices.

Core Features & Use Cases

  • Workflow Audit: Compares local GitHub Actions workflows against upstream versions, flagging stale action versions, missing workarounds, and incorrect triggers.
  • Configuration Audit: Checks various configuration files (pyproject.toml, renovate.json5, .gitignore, etc.) against upstream standards for consistency and completeness.
  • Convention Check: Audits claude.md for adherence to terminology, version formatting, and typing practices.
  • Upstream Contribution Identification: Identifies downstream innovations that could be contributed back to the upstream repomatic project.
  • Use Case: After updating repomatic, run this audit to ensure your project's CI/CD pipelines and configurations are still optimal and haven't fallen behind on best practices or security updates.

Quick Start

Run the repomatic-audit skill to perform a full audit of your repository against the upstream repomatic reference.

Frequently Asked Questions about repomatic-audit

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

FAQPage Schema
How do I audit my GitHub Actions workflows against an upstream reference?

To audit GitHub Actions workflows, you run a repository audit against an upstream reference to identify stale action versions, incorrect triggers, and missing workarounds. This flags outdated CI/CD configurations to ensure alignment.

What does a pyproject.toml configuration audit check for?

A pyproject.toml configuration audit checks local files against upstream standards for consistency and completeness. It identifies outdated configurations and missing settings to prevent project drift.

Can I use this audit to find downstream innovations to contribute back to repomatic?

Yes, you can use this audit to identify downstream innovations that could be contributed back to the upstream repomatic project. It highlights local configurations and workflows that differ from the upstream reference.

When do I need to run a repository alignment audit?

You need to run a repository alignment audit after updating your upstream reference to ensure your project's CI/CD pipelines and configurations remain optimal. This prevents falling behind on best practices or security updates.

Does the convention check verify claude.md typing and version formatting?

Yes, the convention check audits your claude.md file to verify adherence to specific terminology, version formatting, and typing practices. This ensures your project documentation aligns with upstream conventions.

What tools are required to perform a configuration and workflow audit?

Performing a configuration and workflow audit requires the Bash, Read, Grep, Glob, WebFetch, and Agent tools. These execute the necessary file searches, web fetches, and automated reasoning to compare local and upstream files.