skills.rest
jjmendezrodriguez
jjmendezrodriguezCOMMUNITY
Explore all skills by this author →
GitHub

code-git

Generate Conventional Commits and branch names for TypeScript or JavaScript repositories.

Updated Apr 16, 2026
Search Tags:#git#pull request#conventional commits#commitlint#github#branching strategy#husky
One-click install
npx skills add https://github.com/jjmendezrodriguez/jm-claude-plugin --skill code-git
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-git
Source: https://github.com/jjmendezrodriguez/jm-claude-plugin/tree/main/skills/code-git
Command: npx skills add https://github.com/jjmendezrodriguez/jm-claude-plugin --skill code-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces friction and inconsistency in Git and GitHub workflows so teams can ship changes reliably with clean history, predictable PRs, and safer collaboration.

Core Features & Use Cases

  • Conventional Commits: Enforces an actionable commit message format (types, scopes, breaking-change markers) that improves changelog generation and review clarity.
  • Branching Strategy: Provides GitHub Flow and optional Git Flow guidance with strict branch naming rules to keep work organized and reviewable.
  • PR and Repo Hygiene: Establishes practical PR sizing, a PR template, .gitignore defaults for TypeScript/Node, and protections for main plus automation via Husky and commitlint.

Quick Start

Ask the AI for “Is this commit message ok for a change to the API response format, and what would the correct Conventional Commit be?”

Frequently Asked Questions about code-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format conventional commits for a TypeScript repository?▼

Format conventional commits using imperative wording with defined types, scopes, and breaking-change markers to ensure consistent history and automated changelog generation for TypeScript repositories.

What is the best way to enforce conventional commits using Husky and commitlint?▼

Enforce conventional commits by configuring Husky git hooks to run commitlint checks, automatically validating commit message formatting locally before changes are pushed to GitHub.

How do I structure pull requests and branches for consistent GitHub workflows?▼

Structure pull requests by applying strict branch naming rules, utilizing a PR template for sizing, and following GitHub Flow or Git Flow guidance to keep work organized and reviewable.

Can I protect the main branch and automate repository hygiene in JavaScript projects?▼

Yes, protect the main branch by establishing safe merge policies, applying default .gitignore settings, and automating repository hygiene enforcement via Husky hooks and CI checks.

What branching strategy should I use for GitHub Flow versus Git Flow?▼

GitHub Flow provides a straightforward branching strategy for continuous deployment, while Git Flow offers structured guidance for release management, both requiring strict branch naming conventions.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
mvillmowmvillmow
18

quality-run-linters

Run configured linters including mojo-format, markdownlint, and pre-commit checks in check or fix mode.

Community
Intermediate
RedRing2020RedRing2020
1

Git/GitHub ワークフロー

Standardize Git operations, commit formatting, and Pull Request creation for RedRing.

Community
Intermediate