organvm-iv-taxis/github-repository-standards
.build/claude/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 organvm-iv-taxis/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 17, 2026, 2:22 AM7.7s1 file 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
organvm-iv-taxis/shell-history-hygiene
development
VerifiedTrustedCommunity
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/setup-cowork
tools
VerifiedTrustedCommunity
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-lifecycle-patterns
development
VerifiedTrustedCommunity
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-governance-audit
tools
VerifiedTrustedCommunity
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.
12SKILL.mdUpdated Jul 20, 2026