Git & VCS
Git operations, commit helpers, branch management
deft-directive-gh-slice
by deftai
Break a SPECIFICATION.md, PRD, or plan into independently-grabbable GitHub Issues using tracer-bullet vertical slices. Use after spec generation, when the user wants to create implementation tickets, or when breaking work into parallel-assignable issues. Requires the GitHub CLI (gh).
Deft Framework
by deftai
Best practices and guidelines for AI agents in software development
pan-swarm
by eltmon
Start or operate a foreman-driven Overdeck swarm with gated dispatch, merge, observation, and recovery commands.
worktree
by HikaruEgashira
Planが承認/完了した直後に自律的に呼び出す必要があるスキルです。 Trigger: plan approved, plan completed, taskを開始します
steward
by musterd-io
The steward role — the member who keeps the team's declared record honest against what actually shipped. That means the roadmap, decision statuses and documentation prose, checked against merged work and code, corrected in small draft changes with evidence on both sides. Use when you hold the steward role, when reconciling a roadmap or decision status with what shipped, or when a document may have drifted from the code.
delegate-to-zcode
by zrll2
Delegate code writing to ZCode (GLM) while Claude Code decides, verifies and reviews. Use when the user says "delegate to zcode", "let zcode write it", "zcode do this", asks for parallel or autonomous coding, or when a project's CLAUDE.md says to delegate code writing to ZCode. Covers the full loop: preflight, git worktree, work order, run, verify, fix order, review, commit.
ocas-finch
by indigokarasu
'OCAS self-improvement orchestrator (Darwin''s finch — adaptive evolution).
working-with-jj
by YPares
Expert guidance for using JJ (Jujutsu) version control system. Use when working with JJ, whatever the subject. Operations, revsets, templates, debugging change evolution, etc. Covers JJ commands, template system, evolog, operations log, and interoperability with git remotes.
using-git-worktrees
by CommandCodeAI
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
using-fastlane-in-flutter-and-ci
by rodydavis
Automate Flutter app builds and deployments to both the App Store and Google Play using Fastlane with this step-by-step guide.
automate-flutter-app-releases
by rodydavis
Automate your Flutter app releases to beta or production with this handy shell script that handles version bumping, formatting, cleaning, rebuilding, and deployment via Fastlane.
install-flutter-from-git
by rodydavis
Install Flutter SDK via git clone and configure for all platforms
how-to-manage-multiple-flutter-versions-with-git-worktrees-and-z
by rodydavis
Manage multiple Flutter versions efficiently using Git worktrees, eliminating the need for external version managers like FVM.
addressReview
by jthorare
Address PR review comments by spawning domain-specific implementation agents in parallel. Reads from ~/.agentic-workflow/<repo-slug>/reviews/<pr>.json as source of truth, merges any new human GitHub comments, implements fixes, and updates the state file. Can be re-run to continue the review loop.
modular-go
by PsiACE
Practical guidance for Go package design with minimal public APIs, single-responsibility boundaries, stateless-first flow, one-way state transitions, and orchestration-to-capability separation. Use when creating, refactoring, or reviewing Go architecture, package boundaries, interfaces, handlers, managers, builders, and execution flows.
push
by ballred
Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.
review
by IgorGanapolsky
Run a Codex review from Claude Code against the current uncommitted work, a base branch diff, or a specific commit. Use when the user explicitly asks for a Codex review or second reviewer.
Multi-Repo Coordination with Polygraph
by nrwl
Only complete sessions when asked â Only call cloud_polygraph_complete_session when the user explicitly requests it. Do not automatically complete sessions.
chimera-write-the-check-before-the-code
by brcampidelli
A criterion written after the implementation describes the implementation. Write the failing check first, watch it fail, then build.
fleet-coordination
by IgorGanapolsky
Mandatory coordination contract for ANY agent working in IgorGanapolsky/ThumbGate. Runs automatically at session start (SessionStart hook). Before mutating shared repository or vault state, verify no other live agent owns this checkout, has an active vault claim on ThumbGate, or holds a Linear issue covering the same work. Invoke whenever you are about to edit shared files, create branches/worktrees, push, open a PR, or touch ~/Documents/AI-Agent-Sync. Prevents same-repo collisions (files deleted under a live agent, claims overwritten, work lost).
specToProvenPR
by jthorare
Use when turning an approved spec or design doc into production-ready pull requests that are definitively proven to work in the running app. Use for staged multi-phase builds where each stage must be planned, implemented, tested by hand in the running app, evidenced, and only then driven to zero blocking review findings. Triggers include "take this spec to PRs", "ship this design", "prove it works then open the PR", staged epic delivery, and review-loop-until-clean. Also use when tempted to stop a review loop early, treat green tests as proof, or defer findings to a follow-up.
syncDocs
by jthorare
Post-ship documentation updater — refreshes README, ARCHITECTURE.md, CHANGELOG, and AGENTS.md (the repo agent-instructions file) to reflect recent changes.
definition-of-done
by musterd-io
What "done" has to mean before anyone says it — docs, traces and an eval as peers of tests, landed verified against the trunk rather than assumed, and a second party claiming it back. Use when finishing a task, defining a team's done, or when "done" and "merged" have started to drift apart.
seat-workspace-identity
by musterd-io
Give every agent its own workspace with its own git identity, so "who wrote this commit" is answerable without asking anyone — and know the exact line where that goes wrong, because repo-local git config is shared across work trees and the last one written owns everybody's commits. Ships a checker that tells a scoped identity from a shared one. Use when running more than one agent on a repo, when commits carry the wrong author, or when setting up agent workspaces.