skills.rest
MGPowerlytics
MGPowerlyticsCOMMUNITY
Explore all skills by this author →
GitHub

repository-organization

Standardize repository folder structures and governance practices.

Updated Jan 16, 2026
Search Tags:#documentation#CI/CD#Git#maintenance#repository#organization
One-click install
npx skills add https://github.com/MGPowerlytics/nhlstats --skill repository-organization
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repository-organization
Source: https://github.com/MGPowerlytics/nhlstats/tree/main/.github/skills/repository-organization
Command: npx skills add https://github.com/MGPowerlytics/nhlstats --skill repository-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized, maintainable repository structure and governance guidelines to reduce technical debt and streamline onboarding.

Core Features & Use Cases

  • Standardized folder layout and naming conventions across projects.
  • Best practices for branching, commits, CI/CD hygiene, and documentation as code.
  • Use Case: A multi-team project standardizes their repository to enable rapid onboarding and consistent PR reviews.

Quick Start

Align your repository with the standardized structure: create or rename folders to match the recommended layout (.github/, docs/, src/, tests/, scripts/, data/), add a root SKILL.md describing SOPs, and adopt trunk-based development with atomic commits.

Frequently Asked Questions about repository-organization

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

FAQPage Schema
How do I standardize repository layout to reduce onboarding time?▼

To standardize repository layout and reduce onboarding time, align your project with a canonical folder structure including .github/, docs/, src/, tests/, scripts/, and data/, add a root SKILL.md, and adopt trunk-based development with atomic commits.

What folder conventions help reduce technical debt in Git projects?▼

Folder conventions that reduce technical debt in Git projects enforce a canonical structure with designated directories like .github/, docs/, src/, tests/, scripts/, and data/, paired with mandatory SKILL.md files to document standard operating procedures.

How do I set up CI/CD hygiene and documentation as code for a multi-team project?▼

To set up CI/CD hygiene and documentation as code for a multi-team project, enforce consistent folder layouts, adopt trunk-based development with conventional commits, and mandate a root SKILL.md to standardize governance and streamline PR reviews.

Does repository organization work without enforcing conventional commits?▼

Repository organization can function without enforcing conventional commits, but adopting conventional commits and trunk-based development is required to achieve automated governance practices and maintain consistent structure across teams.

What is the best way to structure a repository for maintainability across teams?▼

The best way to structure a repository for maintainability across teams is to apply a standardized folder layout, mandate SKILL.md presence for SOPs, and enforce governance practices through automated CI/CD hygiene and conventional commits.

Related Skills

Explore More Software Engineering Skills→
codebeltnetcodebeltnet
3

trunk-first-repo

Initialize a Git repository with trunk-based development and pull request workflows.

Official
Intermediate
anthony-chaudharyanthony-chaudhary
30

slop-score

Measure code slop across six axes and enforce worst-first remediation.

Community
Advanced
mistakeknotmistakeknot
3

config

Enforce project-wide engineering conventions, settings hygiene, and Git workflows.

Community
Basic
carson-sweetcarson-sweet
6

code-debt

Manage technical debt reduction with behavior-locking tests before refactoring.

Community
Advanced