Git 与版本控制
Git 操作、提交助手与分支管理
update-skill
warpdotdev
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
write-tech-spec
warpdotdev
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
create-pr
warpdotdev
Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.
saga
warpdotdev
Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents. Use this skill whenever the user invokes /saga, asks to autonomously build a sizable feature end-to-end with minimal human intervention, wants a comprehensive spec broken into milestones and tasks with airtight validation criteria before parallelized implementation, or wants an orchestrator to delegate implementation to worker agents while preserving its own context window. Trigger on phrases like "run a saga", "autonomously implement this feature", "spec it out then build it with subagents", "orchestrate this big feature end-to-end", or "build this with workers and validate each step". Also use this skill when asked to continue, resume, or pick up an existing saga from its saga directory (e.g. under ~/.sagas).
new-branch
BuilderIO
Only when explicitly asked for /new-branch or a fresh git branch: stash local changes, update main, and create it. Do not auto-run for normal coding, PR, Builder.io, or Fusion branch workflows.
agentic-jujutsu
ruvnet
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
bm-writing
basicmachines-co
Apply the user-customizable writing standard for Basic Memory notes created or substantially revised by Codex. Use with bm-checkpoint, bm-decide, bm-remember, and other Basic Memory note-writing workflows.
bm-setup
basicmachines-co
Set up the Basic Memory plugin for this project — a short guided interview that configures the project mapping, seeds note schemas, learns or suggests placement conventions, and enables capture reflexes. Use when the user runs /basic-memory:bm-setup, says "set up basic memory", or asks to configure/bootstrap the plugin.
memory-ci-capture
basicmachines-co
Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after bm ci collect prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for bm ci publish.
bm-checkpoint
basicmachines-co
Save a deliberate work checkpoint to Basic Memory with the story, changed files, verification, decisions, blockers, and the next action. Use when the user asks to checkpoint, wrap up, hand off, or remember the state of the work.
pr-create
basicmachines-co
Use when explicitly creating or updating a Basic Memory pull request. This compatibility entry point delegates the full workflow to pull-request and the latest-head Codex gate to pr-review-loop.
bm-orient
basicmachines-co
Resume from an exact Basic Memory checkpoint or orient Codex from current graph and repository evidence.
claude-code-plugins
melodic-software
"Scan a codebase for module-level friction (shallow modules, seam leaks, locality gaps), report candidates as HTML, interview the selected candidate with a Design-It-Twice branch, and hand off the agreed shape. Use when: 'improve architecture', 'find deepening opportunities', 'shallow modules', 'Ousterhout deepening', 'design it twice', 'compare alternative interfaces', 'make code more testable', 'make code more AI-navigable', 'find refactoring opportunities', 'codebase friction', 'module seams', 'locality'. Skip when: a cross-dimension ask ('what should we improve', 'highest-impact improvement', or 'find improvements') routes to /improvement:find; also skip mechanical tidying, diff review, architecture-rule enforcement, or root-cause debugging."
secret-scanner
Sekolah76
Detect exposed secrets, API keys, credentials, and tokens in code. Use before commits, on file saves, or when security is mentioned. Prevents accidental secret exposure. Triggers on file changes, git commits, security checks, .env file modifications.
vulnerability-resolver
Sekolah76
Specialized CVE and vulnerability management for morphir-dotnet. Use when user asks to scan for vulnerabilities, fix CVEs, suppress false positives, review security reports, or manage dependency-check. Triggers include "CVE", "vulnerability", "security scan", "dependency-check", "suppress", "false positive", "CVSS", "security fix".
release-skills
JimLiu
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".
address-github-comments
benjaminasterA
"Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI."
update
vellum-ai
Restart the Vellum assistant and gateway services. Smart branch handling: pulls from main by default, restarts in-place on feature branches, or switches to a specified branch. Pass --pull to force-pull on the current branch.
vellum-github-app-setup
vellum-ai
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity. Use when the user wants the assistant to have its own GitHub identity, or when setting up git push access for the first time.
vellum-pr-readiness
vellum-ai
Prepare Vellum Assistant branches for review by checking git hygiene, PR scope, tests, docs, migrations, Linear linking, and companion repo needs. Use before creating a pull request, splitting work into PRs, or asking whether a branch is ready.
release
vellum-ai
Cut a new release: create the release branch (staging bake), then dispatch the production Release run on that branch.
lint-review
marin-community
Run the read-only infra/lint PR reporter only when invoked by CI or explicitly requested; do not select it for the commit workflow's fix-and-respond review.
ship
BuilderIO
Commit and push the complete current-branch snapshot, open a ready PR, babysit it, merge when clean, then create a fresh branch. Use when the user asks to ship, publish, or hand off local changes. Matching beta and docs paths publish automatically after merge; other production promotion is manual.
resolving-merge-conflicts
mattpocock
"Use when you need to resolve an in-progress git merge/rebase conflict."