Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

git-conventions

Estrellas1

Forks0

Actualizado23 de febrero de 2026, 13:50

Git branch naming, commit message conventions (Conventional Commits), workflow patterns, and common operations. Auto-loaded when working with git.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

hypeJunction

hypeJunction/ai-assistant-starter

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	git-conventions
description	Git branch naming, commit message conventions (Conventional Commits), workflow patterns, and common operations. Auto-loaded when working with git.
category	guideline
user-invocable	false

Git Conventions

Branch Naming

feature/add-user-authentication
feature/TICKET-123-payment-integration
fix/login-redirect-loop
fix/TICKET-456-null-pointer
hotfix/security-patch-xss
chore/upgrade-dependencies
chore/refactor-api-client
experiment/new-caching-strategy

Commit Messages (Conventional Commits)

Attribution: The commit message format and type definitions below are based on the Conventional Commits 1.0.0 specification, licensed under CC BY 3.0.

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description
`feat`	New feature for users
`fix`	Bug fix for users
`docs`	Documentation changes
`style`	Formatting, no code change
`refactor`	Code change, no feature/fix
`perf`	Performance improvement
`test`	Adding/fixing tests
`chore`	Maintenance, deps, config
`ci`	CI/CD changes
`revert`	Reverting previous commit

Subject Line Rules

Use imperative mood ("add" not "added" or "adds")
No period at the end
Max 50 characters (72 for body lines)
Capitalize first letter
Reference issues when applicable

Examples

feat(auth): add OAuth2 login with Google

Implements Google OAuth2 flow for user authentication.
Users can now sign in with their Google accounts.

Closes #123

fix(cart): prevent duplicate items on rapid clicks

Added debounce to add-to-cart button to prevent
race condition when users click rapidly.

feat(api)!: change user endpoint response format

BREAKING CHANGE: User endpoint now returns nested
address object instead of flat fields.

Workflow Patterns

Feature Development

# 1. Start from updated main
git checkout main && git pull

# 2. Create feature branch
git checkout -b feature/my-feature

# 3. Make atomic commits
git add -p
git commit -m "feat(scope): implement X"

# 4. Keep updated
git fetch origin
git rebase origin/main

# 5. Push and create PR
git push -u origin feature/my-feature

Safety Rules

Never rewrite public history (no force push to main)
Never amend pushed commits (only for unpushed)
Never commit sensitive data (.env, credentials, keys)
Use --force-with-lease if force push is needed on feature branch
Keep commits atomic — one logical change per commit
Keep PRs small — under 400 lines ideal

Common Operations

# Undo last commit (keep changes)
git reset --soft HEAD~1

# Stash changes
git stash push -m "work in progress"
git stash pop

# Cherry-pick
git cherry-pick <commit-hash>

# Interactive rebase (squash WIP commits before PR)
git rebase -i HEAD~3

Más de este repositorio

mismo repositorio

finish

hypeJunction/ai-assistant-starter

End-of-session routine. Ensures test coverage, performs self-review, runs validation, and commits cleanly. Use when finishing a unit of work.

2026-03-161

implement

hypeJunction/ai-assistant-starter

Full feature implementation workflow with explore, plan, code, test, validate, and commit phases. Use for new features, enhancements, or significant code changes.

2026-03-161

iterate-pr

hypeJunction/ai-assistant-starter

Iterate on an open PR until CI passes and all review feedback is addressed. Fetches status, categorizes findings by severity, applies fixes, and loops until clean.

2026-03-161

plan

hypeJunction/ai-assistant-starter

Create a detailed implementation plan without writing code. Read-only analysis and planning with user approval gate. Use before implementing features or making significant changes.

2026-03-161

security-review

hypeJunction/ai-assistant-starter

Systematic security audit with confidence-based reporting. Analyzes attack surfaces, checks against OWASP categories, and reports only confirmed or likely vulnerabilities. Use for pre-merge security review or periodic audits.

2026-03-161

validate

hypeJunction/ai-assistant-starter

Run validation checks to ensure code quality, security, and correctness. Supports quick (scoped), full (CI pipeline), fix (auto-correct), and CI mirror modes.

2026-03-161

Git Conventions

Branch Naming

feature/add-user-authentication feature/TICKET-123-payment-integration fix/login-redirect-loop fix/TICKET-456-null-pointer hotfix/security-patch-xss chore/upgrade-dependencies chore/refactor-api-client experiment/new-caching-strategy

Commit Messages (Conventional Commits)

Attribution: The commit message format and type definitions below are based on the Conventional Commits 1.0.0 specification, licensed under CC BY 3.0.

<type>(<scope>): <subject> <body> <footer>

Types

Type

Description

feat

New feature for users

fix

Bug fix for users

docs

Documentation changes

style

Formatting, no code change

refactor

Code change, no feature/fix

perf

Performance improvement

test

Adding/fixing tests

chore

Maintenance, deps, config

ci

CI/CD changes

revert

Reverting previous commit

Subject Line Rules

Use imperative mood ("add" not "added" or "adds")

No period at the end

Max 50 characters (72 for body lines)

Capitalize first letter

Reference issues when applicable

Examples

feat(auth): add OAuth2 login with Google Implements Google OAuth2 flow for user authentication. Users can now sign in with their Google accounts. Closes #123 fix(cart): prevent duplicate items on rapid clicks Added debounce to add-to-cart button to prevent race condition when users click rapidly. feat(api)!: change user endpoint response format BREAKING CHANGE: User endpoint now returns nested address object instead of flat fields.

Workflow Patterns

Feature Development

# 1. Start from updated main git checkout main && git pull # 2. Create feature branch git checkout -b feature/my-feature # 3. Make atomic commits git add -p git commit -m "feat(scope): implement X" # 4. Keep updated git fetch origin git rebase origin/main # 5. Push and create PR git push -u origin feature/my-feature

Safety Rules

Never rewrite public history (no force push to main)

Never amend pushed commits (only for unpushed)

Never commit sensitive data (.env, credentials, keys)

Use --force-with-lease if force push is needed on feature branch

Keep commits atomic — one logical change per commit

Keep PRs small — under 400 lines ideal

Common Operations

# Undo last commit (keep changes) git reset --soft HEAD~1 # Stash changes git stash push -m "work in progress" git stash pop # Cherry-pick git cherry-pick <commit-hash> # Interactive rebase (squash WIP commits before PR) git rebase -i HEAD~3