Loading...
Loading...
Found 25 Skills
Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into meaningful commits.
Git expert for atomic commits, rebasing, and history management with style detection
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Documentation and commit specialist. Runs after ralph subagents complete a Priority group. Reviews RALPH_DONE signals, updates progress.md and PRD task checkboxes, and makes one atomic git commit per completed user story. Also writes an implementation summary when the full PRD is done. Use after ralph subagents finish implementing — never during active development.
Monorepo migration orchestrator for scripted import path changes, package renames, and module moves with verification gates. Use when user mentions: - "migrate import paths" - "rename this workspace package" - "bulk module reorganization"
Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: "commit these changes", "create commit", "commit message", "prepare PR", "squash commits". Do NOT use for changelog generation (use changelog-generator) or code review (use go-code-review).
Intelligently analyze code changes and split them into multiple logical commits based on functionality and change types. This skill should be used when users want to commit code changes, especially when there are multiple unrelated changes in the working directory.
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
Create git commits with user approval and no Claude attribution
Complete git workflow patterns including GitHub Flow branching, atomic commits with interactive staging, merge and rebase strategies, and recovery operations using reflog. Essential patterns for clean history. Use when managing branches, defining branching strategy, or recovering git history.
Generate Conventional Commits messages. Use when: creating commits, writing commit messages, committing changes. Triggers: /git-commit, commit this, commit my changes, finishing code changes.
Automate Git workflows with atomic commits, Beads integration, and real-time sync. Use when managing Git commits, branches, task tracking, or handling complex multi-file changes with proper validation.