How do I install the Github Conventions skill?

Run npx skillmds@latest add jartan-llc/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?

Jartan-LLC (@jartan-llc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Conventions by jartan-llc — Agent Skill

Name: Github Conventions
Author: Jartan-LLC

File contents

GitHub Conventions

CRITICAL: #<number> auto-links to issues/PRs on GitHub. Use 1./2./3. for numbered lists and "Finding 1:"/"Item 1:" for labeled items -- never #1, #2, #3 as markers.

Authentication

Never reconfigure auth transport to unblock a command. Don't switch the remote between SSH and HTTPS, add a credential helper, or push to an explicit URL. A missing key or token scope is a missing credential, not a transport problem -- only the user can supply it, and working around it changes config they never asked you to touch, often globally. Stop and ask.

Branches

Feature branches: feature/<description> or feature/issue-<number> Always check if a branch already exists for an issue before creating a new one.

For sub-issues of a larger feature, branch from the parent feature branch rather than main. Sub-issue work merges back into the parent feature branch, which eventually merges to main.

Commits

Conventional commits format: <type>: description

Types: feat:, fix:, docs:, style:, refactor:, test:, chore: Optional scope: feat(frontend): description

Issues

Templates in .github/ISSUE_TEMPLATE/ -- read them for section structure.

Bug reports: must have label bug
Feature requests: must have label enhancement

Pull Requests

PR template at .github/PULL_REQUEST_TEMPLATE.md -- read it for section structure. Use Closes #<number> to link PRs to issues.

Code Reviews

Reviews are posted as PR comments. See review-format.md for the recommended structure -- severity buckets and the #N footgun to avoid in the summary.

Implementation Plans

Plans are posted as issue comments and saved to .claude/workspace/. See plan-format.md for the recommended structure.

---name: github-conventionsdescription: GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments.---# GitHub ConventionsCRITICAL: `#<number>` auto-links to issues/PRs on GitHub. Use `1.`/`2.`/`3.` for numbered lists and "Finding 1:"/"Item 1:" for labeled items -- never `#1`, `#2`, `#3` as markers.## Authentication**Never reconfigure auth transport to unblock a command.** Don't switch the remotebetween SSH and HTTPS, add a credential helper, or push to an explicit URL. Amissing key or token scope is a missing credential, not a transport problem --only the user can supply it, and working around it changes config they never askedyou to touch, often globally. Stop and ask.## BranchesFeature branches: `feature/<description>` or `feature/issue-<number>`Always check if a branch already exists for an issue before creating a new one.For sub-issues of a larger feature, branch from the parent feature branch rather than main. Sub-issue work merges back into the parent feature branch, which eventually merges to main.## CommitsConventional commits format: `<type>: description`Types: `feat:`, `fix:`, `docs:`, `style:`, `refactor:`, `test:`, `chore:`Optional scope: `feat(frontend): description`## IssuesTemplates in `.github/ISSUE_TEMPLATE/` -- read them for section structure.- **Bug reports**: must have label `bug`- **Feature requests**: must have label `enhancement`## Pull RequestsPR template at `.github/PULL_REQUEST_TEMPLATE.md` -- read it for section structure.Use `Closes #<number>` to link PRs to issues.## Code ReviewsReviews are posted as PR comments. See [review-format.md](review-format.md) for therecommended structure -- severity buckets and the `#N` footgun to avoid in the summary.## Implementation PlansPlans are posted as issue comments and saved to `.claude/workspace/`. See [plan-format.md](plan-format.md) for the recommended structure.

Frequently asked questions

Github Conventions