How do I install the Github Conventions skill?

Run npx skillmds@latest add sakydev/github-conventions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Conventions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Conventions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Conventions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Conventions?

sakydev (@sakydev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Conventions by sakydev — Agent Skill

Name: Github Conventions
Author: sakydev

Github Conventions

Use this skill before creating a branch, writing a commit message, or opening a pull request in this project. Trigger on: "create a branch", "commit this", "write a commit message", "open a PR", "create a pull request", "what should I name this branch", or any time a GitHub workflow action is about to happen.

sakydev 6aece7b 2.2 KB Updated Sep 17, 2026

File contents

GitHub Conventions

Branches

Pattern: <ticket-id>-<short-description> or no-ticket-<short-description>

FLX-123-add-storage-driver
no-ticket-add-agentic-instruction-files

Branch from origin/main. Kebab-case. No slashes. No uppercase.

Commits

Conventional Commits. Ticket number goes after the type.

feat: FLX-1234 add presigned URL download for storage files

- Introduce GetPresignedURL method on StorageService
- Add download endpoint under /storage/:id/download
- Map driver-specific errors to typed pkg/errors responses

Type	When
`feat`	New feature or endpoint
`fix`	Bug fix
`refactor`	Code change, no behaviour change
`test`	Adding or fixing tests
`chore`	Tooling, deps, config
`docs`	Documentation only

Bullet points. No blank lines between them. One commit per logical change. Never --no-verify. Never force-push main.

For any change spanning multiple concerns (new module + config + routing + CI, a multi-file refactor, a ticket touching several layers), split into a sequence of small commits — one per chunkable piece (e.g. skeleton, then config, then handler, then wiring, then infra/CI) — instead of one large commit. Each commit should build/typecheck on its own where practical. Default to splitting; only use a single commit when the change is genuinely one atomic unit (a single small fix, a one-file tweak).

Pull Requests

Title mirrors the commit subject: type: FLX-1234 short description. Under 70 characters.

## What

What does this PR do and why?

## Changes

- Logical changes. Not a file list.

No "this PR" in the title. No trailing period. One PR, one concern. Add Closes #<issue> when fixing a GitHub issue. No Test plan section unless explicitly asked. Never add Claude as a co-author — no Co-Authored-By lines in commits or PR descriptions.

---name: github-conventionsdescription: Use this skill before creating a branch, writing a commit message, or opening a pull request in this project. Trigger on: "create a branch", "commit this", "write a commit message", "open a PR", "create a pull request", "what should I name this branch", or any time a GitHub workflow action is about to happen.---# GitHub Conventions## BranchesPattern: `<ticket-id>-<short-description>` or `no-ticket-<short-description>````FLX-123-add-storage-driverno-ticket-add-agentic-instruction-files```Branch from `origin/main`. Kebab-case. No slashes. No uppercase.## CommitsConventional Commits. Ticket number goes after the type.```feat: FLX-1234 add presigned URL download for storage files- Introduce GetPresignedURL method on StorageService- Add download endpoint under /storage/:id/download- Map driver-specific errors to typed pkg/errors responses```| Type | When ||------|------|| `feat` | New feature or endpoint || `fix` | Bug fix || `refactor` | Code change, no behaviour change || `test` | Adding or fixing tests || `chore` | Tooling, deps, config || `docs` | Documentation only |Bullet points. No blank lines between them. One commit per logical change. Never `--no-verify`. Never force-push `main`.For any change spanning multiple concerns (new module + config + routing + CI, a multi-file refactor, a ticket touching several layers), split into a sequence of small commits — one per chunkable piece (e.g. skeleton, then config, then handler, then wiring, then infra/CI) — instead of one large commit. Each commit should build/typecheck on its own where practical. Default to splitting; only use a single commit when the change is genuinely one atomic unit (a single small fix, a one-file tweak).## Pull RequestsTitle mirrors the commit subject: `type: FLX-1234 short description`. Under 70 characters.```markdown## WhatWhat does this PR do and why?## Changes- Logical changes. Not a file list.```No "this PR" in the title. No trailing period. One PR, one concern. Add `Closes #<issue>` when fixing a GitHub issue. No Test plan section unless explicitly asked. Never add Claude as a co-author — no `Co-Authored-By` lines in commits or PR descriptions.

Frequently asked questions