Git 与版本控制
Git 操作、提交助手与分支管理
transaction-correctness
tursodatabase
How WAL mechanics, checkpointing, concurrency rules, recovery work in tursodb
git-workflow
agno-agi
Git workflow guidance for commits, branches, and pull requests
claude-ecosystem-promoter
majiayu000
Marketing and promotion specialist for Claude ecosystem technology - MCP servers, skills, plugins, and agents. Expert in community engagement, registry submissions, content marketing, and developer relations. Activate on 'promote MCP', 'share skill', 'market plugin', 'launch agent', 'developer marketing', 'MCP registry'. NOT for creating MCPs/skills (use agent-creator), general marketing (use content-marketer), or SEO optimization (use seo-visibility-expert).
sequential-thinking
majiayu000
"Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems."
diff-analysis
majiayu000
Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when: analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact DO NOT use when: quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills. Use this skill for systematic change analysis with risk scoring.
diff-analysis
majiayu000
Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when: analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact DO NOT use when: quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills. Use this skill for systematic change analysis with risk scoring.
Shows you the largest objects in your repo's pack file.
majiayu000
```
commit
mitsuhiko
"Read this skill before making git commits"
update-changelog
mitsuhiko
"Read this skill before updating changelogs"
release-preparation
Caldis
Use when preparing a new Mos release (stable, beta, or alpha) - covers zip packaging, changelog generation, appcast signing, and GitHub release draft creation.
github
HKUDS
"Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries."
changelog
BasedHardware
"Generate changelog entries. Use on releases or PR merges. Parses git commits, categorizes changes, formats changelog entries, and updates CHANGELOG.md."
issue-triage
BasedHardware
"Automate issue triage using ISSUE_TRIAGE_GUIDE.MD. Use when analyzing GitHub issues. Scores issues using triage formula, assigns priority levels, suggests lane assignment, and maps to Omi layers."
pr-automation
BasedHardware
"Automate PR workflows. Use before creating PRs. Generates PR descriptions, validates PR requirements, checks for missing tests/docs, and links issues automatically."
release
tobi
Manage releases for this project. Validates changelog, installs git hooks, and cuts releases. Use when user says "/release", "release 1.0.5", "cut a release", or asks about the release process. NOT auto-invoked by the model.
chrome-devtools
ChromeDevTools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
release
manaflow-ai
"Prepare and ship a cmux release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release."
clay-policy-guardrails
Dicklesworthstone
Implement Clay lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Clay integrations, implementing pre-commit hooks, or configuring CI policy checks for Clay best practices. Trigger with phrases like "clay policy", "clay lint", "clay guardrails", "clay best practices check", "clay eslint".
clay-ci-integration
Dicklesworthstone
Configure Clay CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Clay tests into your build process. Trigger with phrases like "clay CI", "clay GitHub Actions", "clay automated tests", "CI clay".
dcg
Dicklesworthstone
"Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows."
domain-dns-ops
steipete
Domain/DNS ops across Cloudflare, DNSimple, Namecheap for Peter. Use for onboarding zones to Cloudflare, flipping nameservers, setting redirects (Page Rules/Rulesets/Workers), updating redirect-worker mappings, and verifying DNS/HTTP. Source of truth: ~/Projects/manager.
prowler-ci
prowler-cloud
Helps with Prowler repository CI and PR gates (GitHub Actions workflows). Trigger: When investigating CI checks failing on a PR, PR title validation, changelog gate/no-changelog label, conflict marker checks, secret scanning, CODEOWNERS/labeler automation, or anything under .github/workflows.
prowler-changelog
prowler-cloud
Manages changelog entries for Prowler components following keepachangelog.com format. Trigger: When creating PRs, adding changelog entries, or working with any CHANGELOG.md file in ui/, api/, mcp_server/, or prowler/.
prowler-pr
prowler-cloud
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml, pr-check-changelog.yml, pr-conflict-checker.yml, labeler.yml, or CODEOWNERS.