2.5K skills · sorted by relevance
Crafts and generates professional conventional commit messages following Angular/Conventional Commits format. Use when committing changes, writing git commit messages, or when user mentions commit message.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "write a commit message", "create a commit", "format a commit", "what commit type to use", or when preparing changes for a git commit in StreamFlow. Provides commit message format, type conventions, and examples.
The English summary is being prepared. Showing the original description.
Configures and runs git hooks with prek (or the pre-commit it replaces — same `.pre-commit-config.yaml`). Use when adding or troubleshooting git hooks, writing a `prepare-commit-msg` or `commit-msg` stage hook, or authoring `.pre-commit-hooks.yaml` for hook distribution.
The English summary is being prepared. Showing the original description.
Generate commit messages following project conventions and commit staged changes. Use when the user explicitly asks to commit, create a commit, or run /commit.
The English summary is being prepared. Showing the original description.
Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
The English summary is being prepared. Showing the original description.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
The English summary is being prepared. Showing the original description.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
The English summary is being prepared. Showing the original description.
Full validation gate before committing — quality checks, tests, coverage, security scan, changelog, and companion review. Use right before a commit to verify code is ready. Trigger on "pre-commit", "validate before commit", "ready to commit", "run all checks".
The English summary is being prepared. Showing the original description.
中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。
The English summary is being prepared. Showing the original description.
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
The English summary is being prepared. Showing the original description.
Pre-commit code quality review for Unity C# code. Checks against Rules, CODING_STANDARDS.md, NAMING_CONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code", "check my implementation", "pre-commit review", "code review", "check before commit", "is this ready to commit", "review my changes", or any request to validate code quality before committing.
The English summary is being prepared. Showing the original description.
Validate commit messages against the Conventional Commits specification. Auto-detects and installs commitlint CLI if missing. Checks project config or falls back to sensible defaults. Use when validating commit messages, preparing PRs, or enforcing commit conventions.
The English summary is being prepared. Showing the original description.
Drafts board committee charters for Audit and Compensation Committees tailored to public/private status, exchange listing (NYSE/NASDAQ), and governance requirements. Covers composition, independence, authority, meeting procedures, and reporting. Use when creating or updating audit committee charters, compensation committee charters, or corporate oversight committee formations.
The English summary is being prepared. Showing the original description.
Plan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries. To triage an already-dirty working tree and propose commits for existing uncommitted changes, use `planning-commits` instead.
The English summary is being prepared. Showing the original description.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. Use when writing commit messages for a repository that follows Conventional Commits.
The English summary is being prepared. Showing the original description.
Build and create a git commit following this repository's established message format. Use when the user asks to "commit", "commit all changes", "commit and document", or similar. Also applicable when any agent (gemini-cli, codex, qwen, opencode, claude-code) needs to stage and commit a set of changes with a properly structured message.
The English summary is being prepared. Showing the original description.
Batch-commit all uncommitted changes grouped by relevance. Use when multiple accumulated changes need committing. Invoked by saying "commit all" or "commit everything".
The English summary is being prepared. Showing the original description.
Prepare a MYOT commit by writing SuggestedCommit.txt and SuggestedCommitBody.md following Conventional Commits, without actually committing.
The English summary is being prepared. Showing the original description.
Review a week's calendar, tasks, and notes to identify completed commitments, overdue work, stalled projects, and follow-ups. Turn those findings into a realistic next-week plan that accounts for scheduled commitments and available capacity.
Guide Git operations with explicit authorization for history changes and destructive actions. It defines recovery snapshots before discarding work, careful handling of locks and index corruption, and checks that keep unexplained changes out of commits.
Draft investment committee memos for private equity deals, investments in privately held companies. Combine due diligence findings, financial analysis, deal terms, return scenarios, and risks into a structured document with a clear recommendation.
Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.
Split a large commit or branch into a Graphite PR stack, a series of dependent review requests. Group changes by purpose, preserve changes that must stay together, and verify that each lower layer builds and passes tests independently.
Review a branch's commits, combine adjacent changes that belong together, and improve commit messages. A rebuilt history is prepared separately and replaces the original branch only after the user reviews and confirms the proposed changes.