Git 与版本控制
Git 操作、提交助手与分支管理
ralph-operations
mikeyobrien
Use when managing Ralph orchestration loops, analyzing diagnostic data, debugging hat selection, investigating backpressure, or performing post-mortem analysis
code-assist
mikeyobrien
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
arktype
EpicenterHQ
Arktype patterns for discriminated unions using .merge() and .or(), spread key syntax, and type composition. Use when building union types, combining base schemas with variants, or defining command/event schemas with arktype.
git
EpicenterHQ
Git commit and pull request guidelines using conventional commits. Use when creating commits, writing commit messages, creating PRs, or reviewing PR descriptions.
incremental-commits
EpicenterHQ
Break multi-file changes into atomic commits ordered by dependency. Use for refactors, breaking API changes, or features touching 3+ files.
github-issues
EpicenterHQ
GitHub issue comment guidelines for community interaction. Use when responding to GitHub issues, bug reports, feature requests, or any GitHub discussion.
progress-summary
EpicenterHQ
This skill should be used when the user asks questions like "can you summarize", "what happened", "what did we do", "what's the situation", "where are we at", "explain what's going on", "give me an overview", "what's been done", "tell me about this", "walk me through what happened", or any question asking to understand the current state of work or changes. Provides conversational, PR-style summaries with visual diagrams.
yjs
EpicenterHQ
Yjs CRDT patterns, shared types, conflict resolution, and meta data structures. Use when building collaborative apps with Yjs, handling Y.Map/Y.Array/Y.Text, implementing drag-and-drop reordering, or optimizing document storage.
git-safety
tamagui
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
Bard
simota
Developer grumble agent with three AI engines (Codex/Gemini/Claude), each with its own natural voice. Transforms git history, PRs, and milestones into authentic developer monologues, rants, and musings. Use for sprint retrospectives, release commentary, and dev culture posts.
Hearth
simota
個人開発環境の設定ファイル（zsh/tmux/neovim/ghostty等）の生成・最適化・監査。dotfile管理、シェル・ターミナル・エディタの設定が必要な時に使用。
Cipher
simota
ユーザーの意図を言葉の先まで解読。曖昧な要求をコンテキスト・履歴・暗黙の前提から理解し、正確な仕様に変換。要件の深掘り・明確化が必要な時に使用。
git-pushing
mhattingpete
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
dyad:pr-fix
dyad-sh
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
wox-update-changelog
Wox-launcher
Update Wox CHANGELOG.md based on commits since the last release. Use when the user asks to "update changelog", "write release notes", or "summarize changes since last release" and the output must follow the repository's existing changelog format.
render-deploy
tech-leads-club
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
nx-ci-monitor
tech-leads-club
Monitor Nx Cloud CI pipeline and handle self-healing fixes automatically. Checks for Nx Cloud connection before starting.
gh-address-comments
tech-leads-club
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
gh-fix-ci
tech-leads-club
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
ln-003-push-all
levnikolaevich
"Commit and push ALL changes (staged + unstaged + untracked) to the remote repository"
ln-512-tech-debt-cleaner
levnikolaevich
"Automated tech debt cleanup worker (L3). Reads codebase audit findings, applies safe auto-fixes for low-risk issues (unused imports, dead code, commented-out code, deprecated aliases). Confidence >=90% only. Creates single commit with summary."
ln-400-story-executor
levnikolaevich
"Orchestrates Story tasks. Prioritizes To Review -> To Rework -> Todo, delegates to ln-401/ln-402/ln-403/ln-404. Sets Story to To Review when all tasks Done (NOT Done — quality gate handles that). Metadata-only loading up front."
changelog
JetBrains
Maintains IdeaVim changelog (CHANGES.md) and build.gradle.kts changeNotes. Use when updating changelog, documenting releases, or reviewing commits/PRs for changelog entries.
git-workflow
JetBrains
IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Use when creating commits, managing branches, creating pull requests, reviewing git history, or any git-related activity in the IdeaVim project.