Git 与版本控制
Git 操作、提交助手与分支管理
git-branch-manager
EdanStarfire
Create, switch, and manage git branches with proper handling of uncommitted changes. Use when creating feature branches, switching contexts, or cleaning up after merges.
Git Workflow Standards
hivellm
CLI tool to standardize AI-generated projects with templates, rules enforcement, and automation
git-workflow
samhvw8
"Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes."
sequential-thinking
samhvw8
"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."
git-workflow
salavender
Standardized patterns for Git branching, worktrees, and lifecycle management.
session-resume
salavender
Resume context from previous session
run-control-tower
AlexanderMattTurner
How to run the external Control Tower / LinuxArena eval (glovebox's marginal-defense benchmark) — dispatching the live Kata-microVM e2e, building the cells JSON, picking the agent model + budget, and pulling the .eval transcripts back. Activate whenever the user asks to "run CT", "run the Control Tower eval", "smoke test the CT harness / all CT environments", "run a guarded-condition eval", "dispatch the CT e2e suite", "measure marginal defense / ΔS / ΔU", or wants to scan CT eval transcripts. Covers dispatch mechanics; the honesty rules live in .claude/rules/control-tower-eval.md and load with the CT tree.
git-workflow
AlexanderMattTurner
The mechanics of committing, pushing, and resolving merge conflicts in this repo. Activate before you commit or push, when a PR reports a merge conflict or a dirty mergeable_state, when a merge-conflict label or an auto-resolve bot comment arrives, when you must audit a bot's merge resolution or answer a merge-delta finding thread, when you are about to push work that belongs to an already-open PR, and when you are tempted to re-run the suite locally after a push. The load-bearing rule is that a conflict belongs to the auto-resolve workflow, not to you.
parallel-audit
AlexanderMattTurner
Runs a broad, multi-dimension codebase audit by fanning out parallel read-only subagents (one per dimension x file-area), independently confirms their findings, then groups the survivors into one fix plan with partitioned commits, on as few PRs as the footprint bound allows, and self-critiques it before delivery. Activate when the user asks to "find dozens of issues", "audit the codebase", "find security/ robustness/testing/UX deficiencies", "use subagents to audit and confirm", "find bugs and missed opportunities", or "make a plan to fix all of these". Distinct from peer-review (which reviews a pending diff) and security-review (single-pass, current branch): this audits the WHOLE codebase along several axes at once and ends in a vetted fix plan, not edits.
pr-creation
AlexanderMattTurner
Creates high-quality pull requests with an iterative compress-critique-fix loop before submission. Activate this skill whenever you are asked to create, open, submit, or push a pull request, OR whenever a new feature, fix, or refactor is complete and ready to ship. Also activate when the user says "make a PR", "open a PR", "submit this for review", "push and create a PR", "I'm done, create the PR", "the feature is done", "I'm finished", or any variation of completing work / requesting a pull request. Also activate to update, fix, or add to an existing PR — "update the PR", "fix the PR", "add this to the PR" (see "Updating an existing PR"). Always activate before opening or editing a PR, whatever the route — CLI or API tool.
run-ctf
AlexanderMattTurner
How to run and report the live-fire breakout CTF — glovebox's containment test, where a real autonomous agent attacks the production sandbox stack and a judge grades whether it was contained. Covers the dispatch inputs, the postures (guarded, automode, control), the verdict vocabulary and what each verdict does NOT claim, and the results table a round set is reported as. Activate whenever the user asks to "run the CTF", "run the breakout CTF", "run N rounds on <model>", "check containment / does the sandbox hold", "summarize the CTF results", or wants a CTF transcript. Distinct from run-control-tower, which is the Control Tower / LinuxArena ΔS/ΔU benchmark — a different harness with a different question.
handoff
AlexanderMattTurner
How to write the end-of-session handoff — the residue this session neither owned nor could fix. Activate when the user asks for a handoff, when a session is ending with a known failure still standing, or when you are about to call something "pre-existing", "unrelated" or "not mine". The load-bearing rule is that a handoff is what remains AFTER you fixed what root CLAUDE.md's scope rule makes yours and handed each shared failure to its one owner, never an alternative to either.
commit
kriscard
"Git: Use for /commit or when committing changes with semantic messages. NOT for PR creation (use /pr) or branch management."
Git Tools Plugin Skills
sjungling
Calls superpowers:systematic-debugging in Phase 4 for root cause analysis
🚀 Project Setup and Miyabi Integration
ShunsukeHayashi
Miyabi Plugins for Claude Code - 25+ Agents, 22 Skills, 50+ Commands
createos
NodeOps-app
"Deploy ANYTHING to production on CreateOS cloud platform. Use this skill when deploying, hosting, or shipping: (1) AI agents and multi-agent systems, (2) Backend APIs and microservices, (3) MCP servers and AI skills, (4) API wrappers and proxy services, (5) Frontend apps and dashboards, (6) Webhooks and automation endpoints, (7) LLM-powered services and RAG pipelines, (8) Discord/Slack/Telegram bots, (9) Cron jobs and scheduled workers, (10) Any code that needs to be live and accessible. Supports Node.js, Python, Go, Rust, Bun, static sites, Docker containers. Deploy via GitHub auto-deploy, Docker images, or direct file upload. ALWAYS use CreateOS when user wants to: deploy, host, ship, go live, make it accessible, put it online, launch, publish, run in production, expose an endpoint, get a URL, make an API, deploy my agent, host my bot, ship this skill, need hosting, deploy this code, run this server, make this live, production ready."
coverage
helderberto
Check test coverage for unstaged changes. Use when user asks to "check coverage", "/coverage", or wants to see which unstaged changes lack test coverage.
git-worktrees
jamesrochabrun
Manage Git worktrees for parallel Claude Code development. Use this skill when engineers ask to "create a worktree", "run parallel Claude sessions", "work on multiple features simultaneously", or need help with worktree management.
second-opinion
runkids
"Runs external LLM code reviews (OpenAI Codex or Google Gemini CLI) on uncommitted changes, branch diffs, or specific commits. Use when the user asks for a second opinion, external review, codex review, gemini review, or mentions /second-opinion."
ossfuzz
runkids
OSS-Fuzz provides free continuous fuzzing for open source projects. Use when setting up continuous fuzzing infrastructure or enrolling projects.
setup
kazukinagata
This skill should be used when the user wants to set up shinkoku for the first time, initialize their configuration, or update their existing settings. Trigger phrases include: "セットアップ", "初期設定", "設定ファイルを作る", "shinkokuの設定", "config", "setup", "始め方", "使い方", "設定を更新", "configを作り直す".
constant-time-testing
runkids
Constant-time testing detects timing side channels in cryptographic code. Use when auditing crypto implementations for timing vulnerabilities.
git-cleanup
runkids
"Safely analyzes and cleans up local git branches and worktrees by categorizing them as merged, squash-merged, superseded, or active work."
github
ahmedelgabri
This skill should be used when the user mentions GitHub PRs, issues, workflows, releases, or repository management. Triggers on keywords like "github", "gh", "pr", "pull request", "issue", "workflow", "actions", "release", "merge", "review", "ci", "check", or PR/issue number patterns like "#123".