This skill should be used when the user asks to "create README", "add license", "setup contributing guide", "create security policy", "add code of conduct", "generate github templates", or mentions repository documentation files. Provides comprehensive professional templates for enterprise-grade repository structure.
From repo-structurenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin repo-structureThis skill uses the workspace's default tool permissions.
references/variable-reference.mdtemplates/ci/node-ci.yml.templatetemplates/ci/python-ci.yml.templatetemplates/github/CODE_OF_CONDUCT.md.templatetemplates/github/CONTRIBUTING.md.templatetemplates/github/LICENSE.Apache-2.0.templatetemplates/github/LICENSE.MIT.templatetemplates/github/README.md.templatetemplates/github/SECURITY.md.templateDispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Professional, enterprise-grade templates for repository documentation and configuration files.
This skill provides battle-tested templates that follow official standards and best practices:
All templates support intelligent variable substitution and context-aware generation.
Located in templates/github/:
Variable substitution:
{{PROJECT_NAME}} - From git remote or directory name
{{DESCRIPTION}} - From package.json/pyproject.toml or prompt
{{AUTHOR_NAME}} - From git config or settings
{{LICENSE_TYPE}} - From settings or prompt
{{TECH_STACK}} - Detected stack (comma-separated)
{{CI_BADGE}} - Appropriate CI badge markdown
{{COVERAGE_BADGE}} - Coverage badge if tool detected
Support for top 5 OSI-approved licenses:
Selection logic:
defaults.licenseUses Contributor Covenant 2.1 (most widely adopted):
Located in templates/github/.github/:
Located in templates/configs/:
Universal editor configuration:
Stack-adaptive patterns:
__pycache__/, *.pyc, venv/, .pytest_cache/node_modules/, dist/, .env, *.logvendor/target/, Cargo.lock (for binaries).DS_Store, IDE files, OS artifacts.flake8, pyproject.toml (black, mypy).eslintrc.json, .prettierrctsconfig.json.golangci.ymlLocated in templates/ci/:
test.yml - Run tests on push/PRlint.yml - Code quality checksrelease.yml - Automated releases on tagssecurity.yml - CodeQL scanning, dependency reviewStack-adaptive:
.gitlab-ci.yml with stages: test, lint, build, deploy.circleci/config.yml with workflowsProvider detection:
defaults.ci_providerLocated in templates/docs/:
mkdocs.yml with Material themedocusaurus.config.jsSelection criteria:
Analyze repository to gather context:
# Detect tech stack
bash $CLAUDE_PLUGIN_ROOT/skills/tech-stack-detection/scripts/detect-stack.sh
# Read git config
git config user.name
git config user.email
git config remote.origin.url
# Parse package manifests
# package.json, pyproject.toml, Cargo.toml, go.mod
Resolve template variables with intelligent fallbacks:
{{PROJECT_NAME}}:
1. Extract from git remote URL
2. Use directory name
3. Fallback: "my-project" + warning
{{AUTHOR_NAME}}:
1. Config: author.name
2. Git config: user.name
3. Prompt interactively
{{DESCRIPTION}}:
1. Parse from package.json/pyproject.toml
2. Prompt interactively
{{LICENSE_TYPE}}:
1. Config: defaults.license
2. Detect from existing LICENSE
3. Recommend: MIT
4. Prompt if ambiguous
Render template with resolved variables:
# Using the generation script
bash $CLAUDE_PLUGIN_ROOT/scripts/generate-template.sh \
--template "github/README.md" \
--output "./README.md" \
--vars "project_name=my-project,author=Nuno"
Generate appropriate badges based on available data:
Always include:
Conditional:
Using shields.io:
Support for external template sources:
Configuration:
templates:
source: "custom"
custom_repo_url: "https://github.com/org/templates"
merge_strategy: "override" # or "merge"
Repository structure:
custom-templates/
├── github/
│ ├── README.md.template
│ ├── CONTRIBUTING.md.template
│ └── ...
├── configs/
│ └── .gitignore.template
└── ci/
└── github-actions/
└── test.yml.template
Loading order:
merge_strategy: "override" → custom completely replaces embeddedmerge_strategy: "merge" → custom overrides only matching filesTemplates use Mustache-style syntax:
# {{PROJECT_NAME}}
{{DESCRIPTION}}
## Installation
{{#PYTHON}}
```bash
pip install {{PROJECT_NAME}}
{{/PYTHON}}
{{#JAVASCRIPT}}
npm install {{PROJECT_NAME}}
{{/JAVASCRIPT}}
Licensed under {{LICENSE_TYPE}}.
**Conditional blocks:**
- `{{#PYTHON}}...{{/PYTHON}}` - Include if Python detected
- `{{^TESTING}}...{{/TESTING}}` - Include if NOT testing
- `{{#HAS_CI}}...{{/HAS_CI}}` - Include if CI configured
## Template Quality Standards
All templates follow:
### Official Sources
- **Contributor Covenant** for CODE_OF_CONDUCT
- **OSI-approved** licenses
- **GitHub recommended** issue/PR templates
- **EditorConfig** official specification
### Best Practices
- Clear, professional language
- Actionable instructions
- No assumptions about tech stack
- Accessibility considerations (clear headings, alt text)
### Consistency
- Markdown formatting (ATX headings, fenced code blocks)
- Consistent variable naming
- Uniform badge placement
- Standard section ordering
## Usage Examples
### Generate Complete Documentation Set
```markdown
Create complete GitHub documentation:
1. README.md (adaptive to project type)
2. LICENSE (MIT)
3. CONTRIBUTING.md
4. CODE_OF_CONDUCT.md (Contributor Covenant 2.1)
5. SECURITY.md
6. .github/ISSUE_TEMPLATE/bug_report.md
7. .github/ISSUE_TEMPLATE/feature_request.md
8. .github/PULL_REQUEST_TEMPLATE.md
For Python project, create:
1. .editorconfig
2. .gitignore (Python patterns)
3. pyproject.toml (black, mypy configs)
4. .flake8
5. .github/workflows/test.yml (pytest, coverage)
For Node.js project on GitHub:
1. Detect package.json (has test script, eslint config)
2. Create .github/workflows/test.yml (npm test, eslint)
3. Create .github/workflows/release.yml (semantic-release)
4. Add CI badge to README
For complete template contents and patterns:
references/template-library.md - All template contentsreferences/variable-reference.md - Complete variable documentationreferences/badge-patterns.md - Badge generation patternsBrowse actual templates:
templates/github/ - GitHub documentation templatestemplates/configs/ - Configuration file templatestemplates/ci/ - CI/CD workflow templatestemplates/docs/ - Documentation site templatesSee generated examples:
examples/python-project/ - Complete Python project structureexamples/nodejs-project/ - Complete Node.js project structureexamples/go-project/ - Complete Go project structureThis skill works with:
Template generation is orchestrated by the structure-architect agent using this skill's knowledge and resources.