github-project_skill

This skill helps you create and configure GitHub repositories, enforce branch rules, and automate project setup for collaborative development.

Python

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill questnova502/claude-skills-sync --skill github-project

SKILL.md4.9 KB

Overview

This skill provides practical templates and verification steps for GitHub repository setup, branch protection, CODEOWNERS, dependency automation, and PR merge troubleshooting. It streamlines creating new repositories and applying consistent collaboration policies. Use it to standardize documentation, CI requirements, and automated update workflows across projects.

How this skill works

The skill inspects repository layout, presence of required docs, collaboration files, dependency automation configs, and release workflows. It provides asset templates to copy into .github and root, and recommends running a verification script to validate settings against best practices. Guidance covers branch protection rules, auto-merge workflows, and CODEOWNERS configuration to enforce review and merge policies.

When to use it

Creating a new GitHub repository with standard files and policies
Migrating default branch or updating branch protection rules
Adding or fixing CODEOWNERS or issue/PR templates
Configuring Dependabot or Renovate and auto-merge workflows
Troubleshooting PR merge failures caused by protection rules or missing checks

Best practices

Copy and customize provided asset templates into .github and project root rather than editing upstream templates directly
Run the verification script (scripts/verify-github-project.sh) after changes to catch missing docs, templates, or automation configs
Keep branch protection rules in sync with CI workflow names to avoid blocked merges
Use CODEOWNERS to assign reviewers by area and reduce merge friction
Configure Dependabot/Renovate with conservative auto-merge rules and required status checks

Example use cases

Set up a new repository: add README, LICENSE, SECURITY.md, CODEOWNERS, and PR/issue templates using provided templates
Enforce branch protection: require CI checks, code owner reviews, and linear history for main branch
Enable automated dependency updates: add dependabot.yml or renovate.json and an auto-merge workflow for safe updates
Resolve blocked PRs: inspect branch rules, required checks, and CODEOWNERS to identify missing approvals or failing jobs

FAQ

Run scripts/verify-github-project.sh against the repository path to check docs, templates, dependency automation, and release configs.

Where should I put CODEOWNERS and PR templates?

Place CODEOWNERS in .github/CODEOWNERS and PR templates in .github/PULL_REQUEST_TEMPLATE.md; copy the provided templates and adjust paths and teams to your project.