Run any Skill in Manus with one click

github-templates

Stars7

Forks0

UpdatedDecember 29, 2025 at 15:28

GitHub repository templates and configuration. Activate when setting up GitHub repos, CONTRIBUTING.md, CODEOWNERS, issue templates, PR templates, or GitHub Copilot instructions.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ilude

ilude/claude-code-config

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Office and Administrative Support Workers, All OtherOffice and Administrative Support Occupations·SOC 43-9199

File Explorer

7 files

SKILL.md

readonly

name	github-templates
description	GitHub repository templates and configuration. Activate when setting up GitHub repos, CONTRIBUTING.md, CODEOWNERS, issue templates, PR templates, or GitHub Copilot instructions.
location	user

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.

GitHub Templates

Guidelines for GitHub repository configuration and community files.

Essential 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

Issue Templates

Place in .github/ISSUE_TEMPLATE/. Use YAML form format for structured input.

Key elements for bug_report.yml:

Description, steps to reproduce, expected/actual behavior (required)
Version, OS dropdown, logs textarea (optional)

Key elements for feature_request.yml:

Problem statement, proposed solution (required)
Alternatives considered, additional context (optional)

Add config.yml to disable blank issues and add contact links.

See assets/bug_report.yml.template for full example.

Pull Request Template

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)

CODEOWNERS

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:

Later rules override earlier ones
Order from general to specific
Use teams (@org/team) over individuals when possible
Review groups MUST have write access to request reviews

Branch Protection

Recommended settings for main/master:

Require pull request reviews - At least 1 approval, dismiss stale reviews, require CODEOWNERS review
Require status checks - Branches must be up to date, select required CI checks
Restrict who can push - Limit to maintainers/admins
Additional - Signed commits (sensitive repos), no force pushes, no deletions

GitHub Actions Basics

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)

Copilot Instructions

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:

Project overview and tech stack
Coding standards and naming conventions
Preferred patterns (repository, service layer, DTOs)
Domain terminology glossary
Common task workflows

See assets/copilot-instructions.md.template for full example.

Dependabot Configuration

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"

.gitattributes

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

Quick Setup Checklist

Templates Location

Asset templates available in this skill's assets/ directory:

CONTRIBUTING.md.template - Contribution guidelines
SECURITY.md.template - Vulnerability reporting process
CODEOWNERS.template - Code ownership patterns
pull_request_template.md.template - PR template
bug_report.yml.template - Bug report issue form
copilot-instructions.md.template - AI assistant context

More from this repository

same repository

api-design-patterns

ilude/claude-code-config

Language-agnostic API design patterns covering REST and GraphQL, including resource naming, HTTP methods, status codes, versioning, pagination, filtering, authentication, error handling, and schema design. Activate when working with APIs, REST endpoints, GraphQL schemas, API documentation, OpenAPI/Swagger, JWT, OAuth2, endpoint design, API versioning, rate limiting, or GraphQL resolvers.

2025-12-297

git-workflow

ilude/claude-code-config

Git workflow and commit guidelines. Trigger keywords: git, commit, push, .git, version control. MUST be activated before ANY git commit, push, or version control operation. Includes security scanning for secrets (API keys, tokens, .env files), commit message formatting with HEREDOC, logical commit grouping (docs, test, feat, fix, refactor, chore, build, deps), push behavior rules, safety rules for hooks and force pushes, and CRITICAL safeguards for destructive operations (filter-branch, gc --prune, reset --hard). Activate when user requests committing changes, pushing code, creating commits, rewriting history, or performing any git operations including analyzing uncommitted changes.

2025-12-297

testing-workflow

ilude/claude-code-config

Testing workflow patterns and quality standards. Activate when working with tests, test files, test directories, code quality tools, coverage reports, or testing tasks. Includes zero-warnings policy, targeted testing during development, mocking patterns, and best practices across languages.

2025-12-297

ansible-workflow

ilude/claude-code-config

Ansible automation workflow guidelines. Activate when working with Ansible playbooks, ansible-playbook, inventory files (.yml, .ini), or Ansible-specific patterns.

2025-12-297

claude-code-workflow

ilude/claude-code-config

Claude Code AI-assisted development workflow. Activate when discussing Claude Code usage, AI-assisted coding, prompting strategies, or Claude Code-specific patterns.

2025-12-297

container-workflow

ilude/claude-code-config

Guidelines for containerized projects using Docker, Dockerfile, docker-compose, container, and containerization. Covers multi-stage builds, security, signal handling, entrypoint scripts, and deployment workflows.

2025-12-297