changelog-generator
Generate changelog entries from git commits, pull requests, or code changes. Use when creating release notes, updating CHANGELOG.md, or documenting what changed in a version.
Script and automate repetitive tasks and workflows.
Generate changelog entries from git commits, pull requests, or code changes. Use when creating release notes, updating CHANGELOG.md, or documenting what changed in a version.
Manage GitHub repositories - create, fork, branch, and file operations using gh CLI
ๅๆ git commit ๅทฎๅผๅนถๆ นๆฎ็จๆทๆไปค่ฟ่ก้ๆ็ๆ่ฝใๅฎๅฏไปฅๆ นๆฎๆๅฎ็ commit ๅฐ HEAD ไน้ด็ๅๆด๏ผไปฅๆๅผบๅคง่่ง่งๆไพ้ซๅ ่ใๆ็ปดๆค็้ๆๅปบ่ฎฎใ
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, ๆๆช, ๆดๆฐๆๆช, sync docs, release, ็ผๅธ, documentation, ๅๆญฅๆไปถ, ๆไปถๆชขๆฅ, doc check, ็ผๅธๅ, before release, ๆบๅ็ผๅธ.
Use when creating "changelog", "release notes", "version updates", generating "CHANGELOG.md", or asking about "git history to changelog", "commit summary", "what changed since last release"
This skill should be used when reviewing GitHub Pull Requests to provide comprehensive code quality, security, and architecture analysis with optional JIRA ticket integration.
SEMPRE use esta skill quando usuario pedir para fazer commit, commitar, criar commit, ou escrever mensagem de commit. Analisa git diffs e gera mensagens seguindo Conventional Commits.
Generates git commit messages following this repository's conventions. Analyzes staged changes and outputs properly formatted commit messages. Use when user asks to write, generate, or format a commit message.
Build and merge .gitignore files using github/gitignore templates with smart project detection. Use when user mentions gitignore, ignoring files, or when detecting projects without .gitignore.
Git ๆไฝ่ผๅฉ๏ผๆไพ commit message ่ฆ็ฏใๅๆฏ็ญ็ฅ่ PR ๆๅผ
Read the code changes in the current Git branch compared to its parent branch, ignoring generated artifacts (`.wat`, `.hir`, `.masm`) and lockfiles (`.lock`). Run `git parent-branch` to print the parent branch name.
Write clear git commits with Conventional Commits format. Detects project conventions from history and config. Guides commit granularity. Use when: (1) Completing working code, (2) Code builds and tests pass, (3) Ready to save, (4) Before pushing, (5) After review feedback. Triggers: automatically when finishing commitable work that builds and passes tests.
Generate comprehensive .gitignore files tailored to specific tech stacks, frameworks, and development environments. Triggers on "create gitignore", "generate .gitignore for", "gitignore for", "ignore files for".
Generates clean, human-readable changelogs and release notes from git commits and file changes. Use when preparing for a release or summarizing recent work.
Executa CodeRabbit CLI em modo prompt-only para revisar alteraรงรตes locais, identificar issues, planejar correรงรตes e validar com testes antes do commit
Detecta drift entre cรณdigo y documentaciรณn. Valida que README, docs, ejemplos y diagramas estรฉn sincronizados con el cรณdigo actual.
Generate lint-staged configuration for running linters on staged Git files. Triggers on "create lint-staged config", "generate lint staged", "lint-staged setup", "staged file linting".
Conventional Commits formatting guide for creating standardized commit messages. Use when Claude needs to create git commits, ensuring consistent message format with type prefixes (feat, fix, docs, chore). Automatically applied during git commit operations to maintain repository history standards.
Validate & guide commit messages following conventional commits specification with custom type definitions and Linear ID support. Use when crafting commit messages to ensure they follow the correct format with type, optional scope, and title. Includes validation of commit types, scope format, and message structure.
Squash all commits in a feature branch into a single commit with an AI-generated summary message. Use when the user wants to clean up their git history before merging, combine multiple commits, or create a single commit from a feature branch.