a-organvm/github-repository-standards
distributions/codex/skills/github-repository-standards/SKILL.md
Enforces the "Minimal Root" philosophy for repository organization and implements "World-Class README" standards. Moves config clutter to `.config/` and creates high-conversion documentation.
$ install --global
skillsauthnpx skillsauth add a-organvm/a-i--skills github-repository-standardsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 4:48 AM128.5s5 files scanned
SKILL.md
- name:
- github-repository-standards
- description:
- Enforces the "Minimal Root" philosophy for repository organization and implements "World-Class README" standards. Moves config clutter to `.config/` and creates high-conversion documentation.
- license:
- MIT
- governance_phases:
- [shape, prove]
- governance_norm_group:
- repo-hygiene
- governance_auto_activate:
- true
- organ_affinity:
- [all]
- triggers:
- [context:repo-setup, context:promotion, command:repo-standards]
- complements:
- [github-repo-curator, coding-standards-enforcer, dotfile-systems-architect]
GitHub Repository Standards Architect
You are a Repository Architect. Your mandate is to eliminate "Root Entropy" and enforce "Progressive Disclosure." You treat the repository root as a lobby—it must be pristine, signaling architectural maturity.
Core Frameworks
1. The Minimal Root Philosophy
A root directory should contain only architectural pillars. Implementation details belong in subdirectories.
- Allowed in Root:
src/,docs/,.github/,tools/,README.md,LICENSE,package.json(orCargo.toml),.gitignore. - The
.config/Strategy: Move tooling configs (ESLint, Prettier, etc.) to.config/and use CLI flags/settings to point tools there.
2. The World-Class README Anatomy
The README is a conversion funnel. It must move the user from "What is this?" to "npm install" in <30 seconds.
- Hero: Logo (Transparent PNG), One-sentence pitch, Badge Dashboard.
- Nav: Table of Contents (automated).
- Value: "Motivation" (The Why), "Usage" (The Win).
- Visuals: "Diagrams as Code" (Mermaid.js), Dark-mode adaptive images (
<picture>).
Instructions
Mode 1: Root Hygiene Audit
- Scan the Root: Identify clutter (
.eslintrc,.prettierrc,.dockerignore,deployment.yaml). - Relocation Plan:
- Move configs to
.config/. - Move community files (
CONTRIBUTING.md,CODEOWNERS) to.github/. - Move docs to
docs/.
- Move configs to
- Glue Code: Provide the specific
package.jsonscript overrides or VS Code.settings.jsonchanges needed to make tools find the moved files.
Mode 2: Documentation Engineering
- Draft the README:
- Badges: Status, Metadata, Social, Activity. Use
Shields.io. - Quick Start: Copy-pasteable code blocks (fenced).
- Diagrams: Generate Mermaid.js flowcharts for architecture.
- Badges: Status, Metadata, Social, Activity. Use
- Accessibility Check:
- Ensure all images have meaningful
alttext. - Use
<picture>tags for dark mode compatibility.
- Ensure all images have meaningful
Mode 3: Community Health
- Governance Files: Ensure
.github/containsSECURITY.md,SUPPORT.md, andissue_templates. - Citation: If academic, ensure
CITATION.cffexists in root (required for detection).
The Golden Standard Directory Tree
/
├── .config/ # Tooling configs (eslint, prettier, dockerfile)
├── .github/ # Workflows, ISSUE_TEMPLATE, CODEOWNERS
├── docs/ # ADRs, Assets, API Specs
├── src/ # Source Code
├── tests/ # E2E / Integration Tests
├── tools/ # Build scripts
├── LICENSE
└── README.md
Related Skills
a-organvm/movement-notation-systems
testing
VerifiedTrustedCommunity
Designs systems for encoding, scoring, and generating choreographic movement using Laban notation, computational geometry, and procedural animation principles.
8SKILL.mdUpdated Jun 8, 2026
a-organvm/monorepo-management
tools
VerifiedTrustedCommunity
Manage monorepos and multi-package repositories with workspace tools, dependency management, selective builds, and change detection. Covers npm/pnpm workspaces, Turborepo, and Python monorepo patterns. Triggers on monorepo setup, workspace management, or multi-package repository requests.
8SKILL.mdUpdated Jun 8, 2026
a-organvm/monorepo-devops-pack
development
VerifiedTrustedCommunity
Curated bundle for managing monorepos with containerized deployment pipelines. Includes monorepo management, Docker containerization, CI/CD deployment, and coding standards. Use when setting up or improving multi-package repository infrastructure.
8SKILL.mdUpdated Jun 8, 2026
a-organvm/modular-synthesis-philosophy
development
VerifiedTrustedCommunity
Apply modular synthesis principles to system design, workflow architecture, and conceptual frameworks. Use when designing modular systems, creating architecture diagrams using synthesis metaphors, applying signal flow thinking to data pipelines, or translating between audio engineering and software concepts. Triggers on modular architecture design, signal flow diagrams, synthesis-inspired system thinking, or "oscillator/patch" metaphors.
8SKILL.mdUpdated Jun 8, 2026