Loading...
Loading...
Found 116 Skills
Quick reference card for all genshijin modes, skills, and commands. Displayed only once, no mode changes, no state persistence. Activate with "/genshijin-help", "原始人ヘルプ", or "原始人の使い方".
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
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.
Generate ultra-compact commit messages. Follows the Conventional Commits format with subject ≤50 characters, prioritizing "why" over "what". Supports both Japanese and English. Trigger with "Make a commit message", "/commit", or "/genshijin-commit". Auto-trigger candidate when staging changes.
Conventional Commits standard for consistent commit messages. Use when committing code, reviewing commit history, or setting up git workflows. Includes commit types, scopes, and breaking change format.
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.
Apply Spatie's version control conventions when creating commits, branches, pull requests, or managing Git repositories; use for naming repos, writing commit messages, choosing branch strategies, and merging code.
Generate professional git commit messages following Conventional Commits specification. Use when user asks to commit changes or write a commit message.
Refines code changes for better reviewability. Validates change cohesion (no mixed concerns), generates clear commit messages, creates PR/MR with reviewer-focused descriptions. Use when committing, reviewing, creating PR/MR, or mentions "commit", "review", "PR", "MR", "pull request", "merge request", "refine", "提交", "审查".
Generate clear, conventional commit messages from staged changes. Use when the user asks to commit or needs a commit message.
Review local git changes and perform a light code review. If no issues are found, commit the changes. Does NOT write or modify code — only reviews and commits. Optionally accepts a commit message header as an argument.
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or runs /commit-staged or /commit-creator commands.