Loading...
Loading...
Found 8 Skills
[Hyper] Create one or more Conventional Commits from the current repository state. Inspect staged and unstaged changes, group them into logical change sets, generate a compliant message per group, and commit each group separately in sequence.
Stage all changes, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream.
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Supports commands: [commit|commit_a commit_b] [--verify] [--apply] [--commit] Interactive git diff review skill. Parses git diff output into individual hunks, presents each hunk to the user with analysis for accept/reject decisions, verifies complete coverage, and generates a Markdown review report.
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.
Analyzes the working tree, writes a Conventional Commit message, then commits and pushes. Invoked manually only.
A Git workflow assistant toolkit. Use this skill when the user asks to generate a commit message, commit or push code changes, create or switch branches based on a Chinese description, create or update a PR/MR for a target repository, merge a PR/MR by number and update the main branch, tag a branch with a version and push it, tag an already merged stable branch and create a GitHub/GitLab Release by default (the release phase after pr-merge), slim down the current Git repository into a shallow clone, or pull and categorize GitHub starred repositories. It also handles vague requests such as "write a commit message," "commit this," "create a branch for XX," "open a PR," "merge the PR," "create a tag," "publish a release," "publish a version," "slim down the repository," and "categorize my starred repositories."
Write Japanese Conventional Commit messages from staged changes. Use when invoked as `$commit-ja` or `/commit-ja`, attached as a skill, or named as the project's commit convention. Create commits when requested.