repo-skill

To reuse automation workflows across multiple repositories, you can define a centralized SKILL.md file in your repo configuration. This allows standard automation patterns like onboarding and checks to be discovered and activated across different projects.

A repo-level skill configuration is for reducing duplication by allowing teams to publish reusable capabilities once. By placing a root SKILL.md with YAML frontmatter in a repository, teams can apply shared development tasks across multiple projects.

To set up a shared repository skill for team onboarding, copy a repo-level SKILL.md into your project root. Include YAML frontmatter with name and description, and optionally add scripts, references, and assets directories to tailor the automation behavior.

You do not need external dependencies to apply repo-level configs to your projects. The skill operates independently by requiring only a root SKILL.md file with YAML frontmatter to activate shared automation patterns across your repositories.

You can extend repo-level skill behavior by adding optional scripts, references, and assets directories alongside the root SKILL.md file. These extensions allow you to tailor standard automation patterns specifically for each repository's requirements.

The best way to standardize scaffolding tasks across projects is using centralized skill definitions in a repo-level config. By maintaining a single SKILL.md, teams can ensure consistent onboarding and scaffolding automation applied uniformly across multiple repositories.