Loading...
Loading...
Found 319 Skills
Stage and commit the intended changes with a clear message.
Bind the current directory to a MOM project so captured memories are scoped to it. Use when the user wants to set up project scoping, bind a repo, declare a project id, rebind a directory, or asks about .mom-project.yaml.
This skill should be used when the user says "commit my changes", "commit this", "create a commit", "git commit", "save my work", or mentions committing code.
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
Safely clean merged and stale git branches with explicit confirmations.
This skill should be used when the user: - Wants to work on multiple branches simultaneously or in parallel - Needs to start a new feature/task while preserving current work - Asks about git worktree operations (create, remove, list, clean) - Mentions "twig" commands (add, remove, clean, list, init) - Wants to carry or move uncommitted changes to a new branch - Wants to copy/sync changes between branches - Needs to isolate work in a separate directory - Asks about switching context without stashing - Wants to clean up old/merged branches and their worktrees - Says phrases like "new worktree", "create worktree", "branch off", "work on something else", "start new work", "parallel work", "separate workspace", "another branch" Use this skill for ANY worktree-related operation, not just when explicitly asking about twig.
Planが承認/完了した直後に自律的に呼び出す必要があるスキルです。 Trigger: plan approved, plan completed, taskを開始します
DubStack CLI reference. Use for managing stacked changes (git branches). Covers creating stacks, navigating, submitting PRs, rebasing (restacking), and undoing mistakes.
Execute use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.
Narrative templates for git history documentation. Used by /git:code-story command.
Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
Analyze, plan, and execute Clay SDK upgrades with breaking change detection. Use when upgrading Clay SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade clay", "clay migration", "clay breaking changes", "update clay SDK", "analyze clay version".