GitHub repository templates and configuration. Activate when setting up GitHub repos, CONTRIBUTING.md, CODEOWNERS, issue templates, PR templates, or GitHub Copilot instructions.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Guidelines for GitHub repository configuration and community files.
| File | Purpose | Required | |------|---------|----------| | README.md | Project overview | MUST | | LICENSE | Legal terms | MUST for open source | | CONTRIBUTING.md | Contribution guidelines | SHOULD | | CODE_OF_CONDUCT.md | Community standards | SHOULD | | SECURITY.md | Vulnerability reporting | MUST for public repos | | CODEOWNERS | Review assignments | RECOMMENDED | | .github/copilot-instructions.md | AI coding assistant context | RECOMMENDED |
Place in .github/ISSUE_TEMPLATE/. Use YAML form format for structured input.
Key elements for bug_report.yml:
Key elements for feature_request.yml:
Add config.yml to disable blank issues and add contact links.
See assets/bug_report.yml.template for full example.
Place at .github/pull_request_template.md.
## Summary
<!-- Brief description of changes -->
## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update
## Testing
<!-- How was this tested? -->
## Checklist
- [ ] Tests pass locally
- [ ] Documentation updated
- [ ] No breaking changes (or documented)
Place at .github/CODEOWNERS or CODEOWNERS in root.
# Default owners
* @org/team-leads
# Directory ownership
/src/ @org/developers
/docs/ @org/tech-writers
# File patterns
*.js @org/frontend-team
*.py @org/backend-team
# Specific files
/config/prod.yml @org/devops @security-lead
Rules:
@org/team) over individuals when possibleRecommended settings for main/master:
Place workflows in .github/workflows/.
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- run: npm test
Common triggers: push, pull_request, schedule (cron), workflow_dispatch (manual)
Place at .github/copilot-instructions.md for workspace-level AI context.
Purpose: Project-specific context for GitHub Copilot including tech stack, coding standards, patterns, and domain terminology.
Key sections:
See assets/copilot-instructions.md.template for full example.
Place at .github/dependabot.yml.
version: 2
updates:
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
open-pull-requests-limit: 10
labels: ["dependencies"]
groups:
dev-dependencies:
dependency-type: "development"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"
Place in repository root for consistent line endings.
* text=auto
*.sh text eol=lf
*.bat text eol=crlf
*.png binary
*.jpg binary
*.pdf binary
package-lock.json -diff
yarn.lock -diff
.github/ISSUE_TEMPLATE/.github/pull_request_template.md.github/workflows/Asset templates available in this skill's assets/ directory:
CONTRIBUTING.md.template - Contribution guidelinesSECURITY.md.template - Vulnerability reporting processCODEOWNERS.template - Code ownership patternspull_request_template.md.template - PR templatebug_report.yml.template - Bug report issue formcopilot-instructions.md.template - AI assistant contextSearch for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer