Claude Code skills¶

This repository includes Claude Code skills that bring repomatic workflows into Claude Code as slash commands. Downstream repositories can install them with:

$ uvx -- repomatic init skills

To install a single skill:

$ uvx -- repomatic init skills/repomatic-topics

Selectors use the same component[/file] syntax as the exclude config option in [tool.repomatic].

To list all available skills with descriptions:

$ repomatic list-skills
Setup:
  /repomatic-init           Bootstrap a repository with reusable workflows from kdeldycke/repomatic

Development:
  /benchmark-update         Create or update a competitive benchmark page (docs/benchmark.md) comparing the current project against alternatives in the same space. Checks maintenance status, feature accuracy, new candidates, and badge health
  /brand-assets             Create and export project logo/banner SVG assets to light/dark PNG variants. Covers the full lifecycle from initial design exploration through SVG creation to themed PNG export. Use when creating logos, banners, or regenerating PNG exports from SVG source files
  /repomatic-deps           Generate dependency graphs, audit pyproject.toml declarations against version policy, explore unused dependency APIs that could simplify code, and modernize code against the changelogs of upgraded dependencies
  /repomatic-topics         Optimize GitHub topics for discoverability by analyzing competition on topic pages

Quality:
  /babysit-ci               Monitor CI tests, lint, autofix, and Nuitka binary-build workflows, diagnose failures, fix code, commit, and loop until all stable jobs pass. Ignores unstable failures

Maintenance:
  /awesome-triage           Triage new issues and PRs on awesome-list repos by applying curation criteria distilled from past decisions
  /file-bug-report          Write a bug report for an upstream project. Exhaustively reads contribution guidelines, issue templates, and community norms before producing a markdown file ready to paste
  /repomatic-audit          Audit downstream repo alignment with upstream repomatic reference, covering workflows, configs, and conventions
  /sphinx-docs-sync         Two-way comparison and synchronization of Sphinx documentation across sibling projects. Discovers discrepancies in conf.py, install.md, index.md toctree, pyproject.toml docs dependencies, extra-deps sections, readme badges, and static assets. Use when you want to align documentation structure, catch stale dependencies, or push improvements across your Sphinx-enabled repositories
  /translation-sync         Detect stale translations in readme.*.md and contributing.*.md files by comparing structure and content against the English source, then draft updated translations for changed sections
  /upstream-audit           Create or update an upstream contributions page (docs/upstream.md) tracking the project's relationship with its dependencies. Discovers merged PRs, reported issues, workarounds, and declined features

Release:
  /av-false-positive        Scan a release on VirusTotal and generate false positive submission instructions for flagged AV vendors
  /repomatic-changelog      Draft, validate, consolidate, and fix changelog entries
  /repomatic-ship           Orchestrate release preparation. Reconcile the changelog, code, and docs to the net release state, then commit, push, and babysit CI until the release PR is built and `main` is green. Stop before the merge. Review-gated in normal use, fully autonomous under `--dangerously-skip-permissions`

Available skills¶

Phase	Skill	Description
Setup	`/repomatic-init`	Bootstrap a repository with reusable workflows
Development	`/benchmark-update`	Create or update a competitive benchmark page comparing the project against alternatives
Development	`/brand-assets`	Create and export project logo/banner SVG assets to light/dark PNG variants
Development	`/repomatic-deps`	Dependency graphs, declaration audit, and changelog-driven code modernization
Development	`/repomatic-topics`	Optimize GitHub topics for discoverability
Quality	`/babysit-ci`	Monitor CI tests, lint, and Nuitka binary-build workflows and loop until all stable jobs pass
Maintenance	`/awesome-triage`	Triage issues and PRs on awesome-list repos (awesome-list only)
Maintenance	`/file-bug-report`	Write a bug report for an upstream project
Maintenance	`/repomatic-audit`	Audit downstream repo alignment with upstream reference
Maintenance	`/sphinx-docs-sync`	Compare and sync Sphinx docs across sibling projects
Maintenance	`/translation-sync`	Detect stale translations and draft updates (awesome-list only)
Maintenance	`/upstream-audit`	Create or update an upstream contributions page tracking the project’s relationship with its deps
Release	`/av-false-positive`	Scan a release on VirusTotal and generate false positive submission instructions
Release	`/repomatic-changelog`	Draft, validate, consolidate, and fix changelog entries
Release	`/repomatic-ship`	Orchestrate release prep: reconcile, commit, push, and babysit CI to a ready-to-merge release PR

Recommended workflow¶

The typical lifecycle for maintaining a downstream repository follows this sequence. Each skill suggests next steps after completing, creating a guided flow:

/repomatic-init — One-time setup: bootstrap workflows, labels, and configs
/repomatic-deps — As needed: visualize the dependency tree
/repomatic-changelog — Before release: draft and validate changelog entries
/repomatic-ship — Release time: reconcile, commit, push, and babysit CI to a ready-to-merge release PR

Walkthrough: setup to first release¶

These steps take a downstream repository from a fresh checkout to its first release, running each skill interactively and approving its actions as you go:

Bootstrap your repository (one-time) with /repomatic-init:
```
/repomatic-init
```
Add changelog entries as you work, with /repomatic-changelog:
```
/repomatic-changelog add
```
Hand the rest to /repomatic-ship: it reconciles the changelog, code, and docs, commits and pushes (rebuilding the release PR), then runs /babysit-ci until main is green, catching Nuitka binary-build breakage. It shows the changelog diff before the commit prompt, so you approve each step as you go:
```
/repomatic-ship
```
On GitHub, merge the release PR with “Rebase and merge”, never squash.

Fully automated workflow¶

Step 3 of the walkthrough is the same skill whether you drive it or not. Under --dangerously-skip-permissions, /repomatic-ship runs the whole release prep hands-off: reconcile, commit, push, and babysit CI until the release PR is green, pausing for nothing. In normal use the permission prompts are the review gate; skipping permissions removes them.

$ claude --dangerously-skip-permissions /repomatic-ship

Warning

--dangerously-skip-permissions disables every permission prompt for the session: Claude Code commits, pushes, and runs shell commands without asking first. Only use it when you trust the repository state, ideally inside a sandbox or disposable checkout.

The judgment-heavy sweep (changelog consolidation, the version read) runs on Opus, while the mechanical CI-fixing loop is delegated to a Sonnet subagent running /babysit-ci. Its autonomous commits carry a Co-Authored-By trailer, and it stops at a green release PR: the final “Rebase and merge” stays yours.

The full sequence, with the parallel passes and the two convergence loops:

        sequenceDiagram
    autonumber
    actor Op as Operator
    participant Ship as repomatic-ship (Opus)
    participant AG as Code and Docs agents
    participant CL as repomatic-changelog
    participant Local as Local checks
    participant Main as main (git)
    participant CI as CI jobs
    participant BCI as babysit-ci (Sonnet)

    Op->>Ship: claude --dangerously-skip-permissions /repomatic-ship

    Note over Ship,CL: Phase 1 reconcile substance, then summarize
    par code
        Ship->>AG: code review (simplify, dedup, harmonize)
    and docs
        Ship->>AG: docs verification
    end
    Ship->>CL: consolidate changelog (reflects final code and docs)

    Note over Ship,Local: Phase 2 local pre-push gate
    loop until all green
        par tests
            Ship->>Local: pytest
        and types
            Ship->>Local: mypy
        and lint
            Ship->>Local: ruff and lint-changelog
        end
        Local-->>Ship: fastest failure
        Ship->>Ship: fix in working tree
    end

    Note over Ship: Phase 3 and 4, version advisory then show diff
    Ship->>Main: Phase 5 commit and push (clean, Co-Authored-By)
    Main->>CI: prepare-release, tests, lint, binaries

    Note over Ship,BCI: Phase 6 babysit (first run mostly green)
    Ship->>BCI: run /babysit-ci (foreground Sonnet)
    loop until main green
        CI-->>BCI: only CI-exclusive failures (platform, Nuitka)
        BCI->>Main: fix and push
    end
    BCI-->>Ship: green
    Ship-->>Op: Phase 7 release PR ready, then Rebase and merge