generating-commit-messages
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
Use this skill proactively when wrapping up a session to prepare the repo for the next agent. Read this before finalizing PRs, closing issues, or ending sessions.
Commit and push changes to GitHub with proper messages. Use when ready to save changes, push to production, or deploy updates to GitHub Pages.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Analisa as issues do GitHub e as classifica por dificuldade.
Link a project to a GitHub repository. Requires authentication
Create user-facing App Store release notes from git history. Use when asked to generate release changelog, App Store "What's New" text, or release notes based on git tags.
Git workflows, branching strategies, and commit conventions
This skill should be used when the user says "commit", "create a commit", "commit changes", "done with changes", "ready to commit", or when Claude has completed implementing a feature or fix and needs to commit the work.
Extract and summarize review comments from GitHub PRs. Use when analyzing PR reviews, checking unresolved issues, or responding to CodeRabbit feedback.
Skill for recording changes to the local repository. Typical use cases include (1) Committing product code and tests after completing a feature or bug fix, (2) Recording structural changes such as architecture updates or ADR drafting, and (3) Staging and committing multiple small maintenance changes or documentation updates.
[DEPRECATED] Worktree CLI is now available via npm - no setup needed
Modifies existing skills for new contexts. Forks skills from repositories, adjusts for local conventions, and customizes behavior while preserving core functionality. Use when a skill is close but not quite right.
Clean up after an issue PR is merged. Merges the PR if needed, removes the worktree, deletes the branch, updates main, and starts a fresh session. Use when asked to clean up an issue, finish an issue, or after a PR is approved.
When asked to commit the codebase, follow these guidelines
Create a GitHub pull request with generated description
Ensures CLAUDE.md, README.md, and CHANGELOG.md are updated before git push operations