Loading...
Loading...
Found 367 Skills
Analyze staged Git changes and generate a concise Chinese commit message that follows repository commit style. Use when the user asks to commit code, generate a commit message, or summarize staged changes into a Chinese Git commit title and bullets.
[Hyper] Push unpushed commits to the remote. Discovers the current or descendant git repositories, checks for commits ahead of upstream, and pushes them. Use when the user wants to push, sync to remote, or send commits upstream.
Analyzes and rewrites prompts for better AI output, creates reusable prompt templates for marketing use cases (ad copy, email campaigns, social media), and structures end-to-end AI content workflows. Use when the user wants to improve prompts for AI-assisted marketing, build prompt templates, or optimize AI content workflows. Also use when the user mentions 'prompt engineering,' 'improve my prompts,' 'AI writing quality,' 'prompt templates,' or 'AI content workflow.'
Write a description to description GitHub Pull Request.
This skill should be used when creating Git commits to ensure they follow the Conventional Commits specification. It provides guidance on commit message structure, types, scopes, and best practices for writing clear, consistent, and automated-friendly commit messages. Use when committing code changes or reviewing commit history.
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Create alpha-forge git worktrees with auto branch naming. TRIGGERS - create worktree, new worktree, alpha-forge worktree.
This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix for a production issue.
This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix finish", or wants to finalize a hotfix and merge it into main and develop.
Generate high-quality git commit messages following Conventional Commits and Chris Beams' Seven Rules. Infers WHY from context and provides clear guidance on structure, scope, and body content.
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /review-pr. Never merge or push to main.
[Git & Release] Update CHANGELOG.md [Unreleased] section with business-focused entries via systematic file review