Loading...
Loading...
Found 127 Skills
Provides git workflow assistance, branch management, and commit message optimization
Guidance for Worktrunk, a CLI tool for managing git worktrees. Covers configuration (user config at ~/.config/worktrunk/config.toml and project hooks at .config/wt.toml), usage, and troubleshooting. Use for "setting up commit message generation", "configuring hooks", "automating tasks", or general worktrunk questions.
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.
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing.
Cria mensagens de commit no estilo Conventional Commits — usar quando o usuário pede "commit", "git commit", ou após mudanças prontas para serem registradas no histórico.
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
Correct naming for a PR
commit changes to git with a message derived from the diff only, ignoring session context like reviews or discussion. Skips hooks with -n by default; --verify runs them. Triggers: /commit, commit changes, save work to git, write a commit message. Flags: --staged/--unstaged for scope, --conventional/--simple for style, --verify to run hooks.
Creates and executes one coherent git commit from staged or selected working-tree changes. Use when the user asks to commit changes, stage and commit a logical change, or create a git commit with an appropriate message. Do not use for a draft-only message request or an operation that only pushes existing commits.
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.
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
Quick reference card for all genshijin modes, skills, and commands. Displayed only once, no mode changes, no state persistence. Activate with "/genshijin-help", "原始人ヘルプ", or "原始人の使い方".