dot-github

Standardize `.github` directory structure and agentic documentation patterns.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill dot-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dot-github
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/dot-github
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill dot-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

dot-github prevents repositories from drifting into inconsistent, unsafe, or unintentionally disruptive .github configurations by standardizing structure and agentic documentation patterns.

Core Features & Use Cases

  • Enforces agentic documentation conventions: Defines how to structure .github/AGENTS.md, workflows, prompts, and instruction scopes so agents can reliably discover and follow repository-specific operating guidance.
  • Improves workflow safety and governance: Recommends disabling workflows via moving them to .github/workflows-disabled/ rather than deleting them, preserving history and reducing operational risk.
  • Reduces common GitHub anti-patterns: Warns against creating .github/README.md (which overrides the repository homepage) and against inventing CODEOWNERS entries.

Quick Start

Load the dot-github skill when creating or updating files under your repository’s .github/ directory to ensure AGENTS.md and workflow documentation follow the required organizational patterns.

Frequently Asked Questions about dot-github

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

FAQPage Schema
How do I standardize a .github directory structure for agentic documentation?

To standardize a .github directory, structure AGENTS.md, workflow documentation, and instruction scopes so agents can reliably discover and follow repository-specific operating guidance without inconsistent configurations.

What is the safest way to disable GitHub workflows without deleting them?

The safest way to disable GitHub workflows is moving them to a .github/workflows-disabled/ directory, which preserves file history and reduces operational risk compared to outright deletion.

Why should I avoid creating a .github/README.md file in my repository?

You should avoid creating a .github/README.md file because it overrides the repository homepage display, which is a common GitHub anti-pattern that disrupts standard repository navigation and visibility.

Do I need to validate mcp-config.json when setting up GitHub governance files?

Yes, you need to validate .github/mcp-config.json when present to enforce guardrails and prevent unsafe repository governance when establishing agentic instructions and workflows.

Can I automatically generate CODEOWNERS entries when standardizing .github configurations?

You should not invent unverified CODEOWNERS entries when standardizing .github configurations, as the guardrails mandate avoiding unverified ownership rules to maintain safe repository governance.

What are common GitHub anti-patterns when configuring repository governance with agents?

Common GitHub anti-patterns include creating a .github/README.md that overrides the homepage, deleting workflows instead of moving them, and inventing unverified CODEOWNERS entries during agentic documentation setup.