Loading...
Loading...
Found 199 Skills
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
Create a git commit following project conventions
Create git commits following the Conventional Commits v1.0.0 specification (conventionalcommits.org). Use when the user asks to commit changes, says "/conventional-commit", or wants a well-structured commit message. Triggers on requests like "commit this", "commit my changes", "create a commit", or any git commit workflow. Analyzes staged/unstaged changes and produces compliant commit messages with proper type, scope, description, body, and footers.
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.
A comprehensive Git assistant skill that provides intelligent branch management, commit message conventions, workflow assistance, and code review guidance. Automatically activates when users perform Git operations or use /git commands.
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages
Generate well-formatted git commit messages following conventional commit standards
Generate feature-based and confidentiality-safe English LinkedIn Experience drafts directly from commit messages. Use when asked to write LinkedIn experience text from real commit activity for all-time or a specific date range (`since`/`until` in YYYY-MM-DD), while avoiding repository statistics and internal/confidential implementation details.
Git version control and GitHub CLI workflows for commits, branches, pull requests, and code reviews with professional commit message practices.
Generates conventional one line commit messages from a git diff
Stage safe changes on the current branch and create a single conventional commit. Skips generated artifacts, caches, logs, and editor cruft. Accepts hints like "only staged", "relevant", or "amend".
Rewrite AI-sounding text so it reads like a human domain expert without changing what it says. Use when editing or reviewing prose, documentation, commit messages, PR descriptions, and summaries for AI tells: not-X-but-Y contrasts, copula avoidance ("serves as", "stands as"), forced triads, em dashes everywhere, inflated significance ("pivotal", "testament", "tapestry"), sales puffery, formulaic "challenges and future outlook" conclusions, canned procedural summaries ("refined for clarity and flow", "preserved X while improving Y"), shallow -ing riders, bold-colon listicles, and stock AI vocabulary. Exhaustively based on Wikipedia's "Signs of AI writing" and WikiProject AI Cleanup.