Loading...
Loading...
Found 154 Skills
Generate appropriate commit messages based on Git diffs
Create an appropriate git commit from the working tree and session history. Default commit messages are in Japanese unless the repo says otherwise (e.g. AGENTS.md).
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.
Analyzes staged and unstaged files from the full working tree, groups them into functional clusters (test, docs, chore, directory prefix), generates a conventional commit message per group, detects common issues (secrets, debug statements, large files), and executes one commit per group sequentially after presenting a multi-commit plan for confirmation. Falls through to a single-commit flow when all detected files resolve to one group. Trigger: When the user says "commit", "smart commit", or /commit.
Session wrap-up. Use when Ane types /wrap-up to close a session. Checks git, errors, and pending actions, delivers a concise status report, then commits and pushes any pending work.
Generate project-level AGENTS.md guides that capture conventions, workflows, and required follow-up tasks. Use when a repository needs clear agent onboarding covering structure, tooling, testing, task flow, README expectations, and conventional commit summaries.
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Create git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.
Generate git commits following Conventional Commits (commitlint). Use when user wants to commit changes.
Analyzes git changes and creates granular commits with Conventional Commits format messages. Detects repository language pattern from recent commits. **MUST ALWAYS be used when creating git commits, regardless of whether the user explicitly requests it or not.**
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
Always apply this skill when committing to git