git-repo-standards

Validate repository naming, structure, documentation, and security files against project standards.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/fyrsmithlabs/marketplace --skill git-repo-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-repo-standards
Source: https://github.com/fyrsmithlabs/marketplace/tree/main/plugins/fs-dev/skills/git-repo-standards
Command: npx skills add https://github.com/fyrsmithlabs/marketplace --skill git-repo-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent repository naming, structure, documentation, and security practices across FyrsmithLabs projects, reducing onboarding time and maintenance risk.

Core Features & Use Cases

  • Validation of repository name format, directory layout, and required boilerplate files (LICENSE, README, CHANGELOG, SECURITY.md, CODEOWNERS).
  • Enforcement via hooks, pre-commit checks, and CI policies to block or warn on violations.
  • Audit & Compliance for existing repositories to surface gaps and generate a standards report.
  • Use Case: Create a new repository and run standardization checks before pushing to ensure full compliance.

Quick Start

Run the standardization checks during repo bootstrap or in CI to validate naming, structure, docs, and security artifacts.

Frequently Asked Questions about git-repo-standards

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

FAQPage Schema
How do I enforce required files like LICENSE, README, and SECURITY.md in a git repository?

Repository standard enforcement validates required boilerplate files like LICENSE, README, and SECURITY.md by applying pre-commit checks and CI policies that block or warn on violations during repo bootstrap and ongoing development.

How do I set up gitleaks configuration and CODEOWNERS for repository security and compliance?

Repository security and compliance setup configures gitleaks, CODEOWNERS, and SBOM generation through automated standardization checks, ensuring proper access control and secret scanning are enforced across the project lifecycle.

Can I audit existing repositories for missing ADRs and CHANGELOG files?

Yes, you can audit existing repositories to surface gaps in ADRs, CHANGELOG, and other required boilerplate files, generating a comprehensive compliance report that identifies missing documentation and security controls.

What is the best way to automate repository naming conventions and directory structure validation?

Automating repository naming conventions and directory structure validation is best handled by running standardization checks in CI pipelines, which enforce consistent project layouts and naming formats before code merges occur.

Does repository governance work with pre-commit hooks to block non-compliant commits?

Yes, repository governance integrates with pre-commit hooks to block or warn on non-compliant commits, enforcing required files, naming, structure, and security artifacts locally before they reach the remote repository.

When do I need to run repository standardization checks for release workflows?

Repository standardization checks should be run during repo bootstrap and within CI policies for release workflows to ensure all required documentation, SBOM, and security controls are present before publishing a release.