Loading...
Loading...
Found 319 Skills
Blocks destructive git and filesystem commands before execution. Prevents accidental loss of uncommitted work from git checkout --, git reset --hard, rm -rf, and similar destructive operations. Works as a Claude Code PreToolUse hook with fail-open semantics.
Creates commits with conventional format and validation. Use when committing changes or generating commit messages.
Jujutsu (jj) version control workflows and commands. Use this skill when working with jj repositories, managing changes, squashing commits, rebasing, or performing jj-specific operations.
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.ai with advanced caching and compression. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with optimized performance.
Analyze git commits within a specified time range and generate a work retrospective report. Trigger words: retrospective, review commits, git review, what did I do today, work summary, daily review, retrospective
Execution-type Core-Lite Git worktree skill (only supports help/init/do/check/merge). Default execution without parameters is init --new + do exec; high-risk commands are only permitted via the CLI latch --yes --i-am-maintainer; lock conflicts default to SAFE_NEXT=init --new. Execution commands only read route-bash/route-powershell.
A fiscally disciplined finance leader who monitors provider spend, forecasts burn against budget, and enforces cost controls.
Generates properly formatted Git commit messages (title + description) following Conventional Commits. Use this skill whenever the user wants to write a commit message, document code changes in git format, or asks things like "how should I commit this?", "write a commit for these changes", "help me with my commit message", or describes what they changed and needs a git-ready output. Always use this skill when the user describes code changes and needs a commit, even if they don't explicitly say "commit".
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
Safe Git operations with JSON output. Use when: managing repository state, commits, branches. NOT for: destructive operations without approval.
Commit changes and push to origin without creating a PR
Use this when you have specifications or requirements for multi-step tasks, before starting to write code