iDiagoValeta

GitHub Practices — Git skill for Claude Code

Git community

Claude Code / OpenCode skill that audits a GitHub repo against best practices (branch protection, rulesets, Conventional Commits, PR and issue templates, Dependabot, release-please) and applies only a.

How to install GitHub Practices

This entry records only its repository, not the path inside it, so there is no exact command to give. Open iDiagoValeta/github-practices and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What GitHub Practices does

Alternatives in Git

Triage Open Pull Requests — Review, label, and act on all open PRs for a repository using parallel review agents 10.8k ★
Merge Dependabot PRs — @description Evaluate and merge dependabot PRs with parallel builds, dependency-aware batching, and transitive 1.6k ★
Createissue — Create GitHub issues using proper templates and conventions 849 ★

README

github-practices

[![CI](https://github.com/iDiagoValeta/github-practices/actions/workflows/ci.yml/badge.svg)](https://github.com/iDiagoValeta/github-practices/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

A Claude Code skill (also for OpenCode and other AI agents) that audits a GitHub repository against best practices and applies only the changes you approve. It is for anyone who maintains a repo and wants branch protection, templates, labels and releases set up right without reading every GitHub doc: install it, run `/github-practices` and review the report.

What it checks

It covers the branching model, branch names, issues and pull requests, Conventional Commits, labels, rulesets, CODEOWNERS, Dependabot and release-please. It does not impose a model: it picks one from the repo and explains why.

Branching model. Detects trunk-based development or Gitflow from the branches and the default branch, and recommends one with its reasons.
Branch protection. Rulesets on the default branch: pull request required, required status checks, no force push, no deletion and linear history in trunk-based development.
Pull requests. Template, median size (250 lines is the target, 500 the warning) and linked issue through a closing keyword.
Branch names. /- (only automated/, internal/ and revert/ may skip the issue), checked against the repo name and the 63 character limit.
Issues. Bug and feature forms that prelabel kind/bug and kind/feature.
Labels. The ten labels the skill expects, from kind/* to breaking and skip-release.
Commits. Conventional Commits in the last 50 non-merge commits and the optional .gitmessage template.
Merge methods. Squash only in trunk-based development, merge commits allowed in Gitflow.
CODEOWNERS. Suggested when the repo has more than one contributor.
Security. Dependabot, secret scann