Git i control de versions
Operacions de Git, assistència per a commits i gestió de branques
nix
i9wa4
Nix commands and package management guide. Use when: - Running nix build, nix run - Adding custom packages - Using nurl for hash acquisition
topology-drift
dwarvesf
Maintainer-only. Use to audit THIS KIT's OWN feature estate against its path map, "run the topology-drift loop", "feature inventory drift". NOT for a consumer/adopter repo, NOT for a target project (/kit:feature-map), NOT for regenerating the registry, NOT for whole-doc prose drift (doc-drift), NOT for one known-missing feature.
git
i9wa4
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
memory-tidy
dwarvesf
Use when auditing, consolidating, or cleaning a repo's .claude/memory store, "dọn memory", "memory tidy", the biweekly memory audit, duplicate or stale memory notes, MEMORY.md index drift, or a scheduled memory-tidy audit. NOT for the built-in machine-local auto-memory under ~/.claude/projects, NOT for editing a single note (just edit it).
session-reflect
i9wa4
End-of-session retrospective skill. Collects today's commits and vault notes, analyzes friction patterns, and proposes improvements to CLAUDE.md and skills. Use when: - User says "session-reflect", "振り返り", or "今日の振り返り" - End of a work session - User asks for improvement proposals
plan-design
i9wa4
Create high-quality, executable implementation plans for complex tasks by combining source digestion, parallel worker investigations, critic+guardian+boss review gates, and beginner-friendly packaging. Use when a user needs a step-by-step plan (not immediate implementation), especially when source material is large, fragmented, or hard for newcomers to understand.
evolution
ZhangHanDong
CRITICAL: Use for makepad-skills self-evolution and contribution. Triggers on: evolve, evolution, contribute, contribution, self-improve, self-improvement, add pattern, new pattern, capture learning, document solution, hooks, hook system, auto-trigger, skill routing, template, pattern template, shader template, troubleshooting template, 演进, 贡献, 自我改进, 添加模式, 记录学习, 文档化解决方案
makepad-basics
ZhangHanDong
CRITICAL: Use for Makepad getting started and app structure. Triggers on: makepad, makepad getting started, makepad tutorial, live_design!, app_main!, makepad project setup, makepad hello world, "how to create makepad app", makepad 入门, 创建 makepad 应用, makepad 教程, makepad 项目结构
fix-ci
ryoppippi
Diagnoses and fixes CI failures with the gh CLI. Use when GitHub Actions checks are red and the failing logs need to be fetched, analysed, and resolved.
create-commits-and-push
ryoppippi
Creates atomic git commits and pushes to remote. Use when you want to commit changes and push without creating a PR (e.g., "commit and push my changes" or "push this up").
merge-main
ryoppippi
Merge the latest main branch into your current feature branch. Use when you need to sync your branch with upstream changes.
create-pr
ryoppippi
Runs the full PR workflow — creates a feature branch, commits, pushes, and opens the pull request. Use when the user asks to create or open a PR ("create a PR", "push this up and open a PR").
commit
ryoppippi
Creates atomic Conventional Commits. Use when committing code changes, splitting hunks into revertable units, or writing commit messages.
ci-triage
AlexanderMattTurner
How to respond when a CI check goes red, a PR check fails, a test is flaky, a job times out, or a webhook reports a failing status — plus how to read GitHub check state at all (gh locally vs mcp__github__* on the web, and why one page of get_check_runs never proves "all green"). Activate whenever a check is red or cancelled, a workflow run failed, a shard timed out, a test is intermittent, you are about to claim a PR is green or mergeable, you are about to re-run a job, or you need a failing job's log. Also activate before dispatching an expensive/live-fire workflow to verify a fix. The load-bearing rule is that a red check is a bug you have not diagnosed yet — "flake", "pre-existing", "unrelated", and "infra" are conclusions you must earn by reading the log, never opening assumptions, and never a licence to re-run.
babysit-prs
AlexanderMattTurner
How to sit on a set of already-open PRs and drive them to landed — building the watch set, reading GitHub's mergeability and queue state correctly, re-arming auto-merge, dispatching fixes for reds, and deciding which wake-ups deserve a reply. Activate when asked to "babysit", "watch", "monitor", "sit on", "keep an eye on", "drive to green", "land" or "merge" one or more open PRs (a named stack included), when asked to re-enable auto-merge on PRs that lost it, when a PR sits in a state you cannot explain (unknown mergeability, auto-merge silently off, a required check that never reports), or when a wake-up arrives from a PR you are already watching. The load-bearing rule is that babysitting lands PRs through the auto-merge path — a direct merge is reserved for a narrow, reproduced fix for a red on main.
mcp-setup
spences10
Setup guide for essential MCP servers. Use when configuring MCP servers or when user asks about search, SQLite, or MCP management.
bubbletea
hmans
Browse Bubbletea TUI framework documentation and examples. Use when working with Bubbletea components, models, commands, or building terminal user interfaces in Go.
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.
managing-artifacts
axiomantic
Use when generating documents, reports, plans, audits, or when asked where to save files. Triggers on "save report", "write plan", "where should I put", "project-encoded path"
using-git-worktrees
axiomantic
"Use when starting feature work that needs isolation from current workspace, setting up parallel development tracks, or before executing implementation plans. Triggers: 'worktree', 'separate branch', 'isolate this work', 'don't mess up current work', 'work on two things at once', 'parallel workstreams', 'sandboxed workspace'."
gh-enrich-pr-description
TrogonStack
Enrich GitHub PR descriptions with root-cause context, related issues/PRs, and CC mentions. Use when creating or editing a PR, when a PR has an empty or sparse description, or when the user asks to improve a PR description.
coding-agent-workflow
luosky
用 GitHub label 驱动本机 agent 处理 issue/PR，daemon 自动监听并派工。包含 setup（一次部署到某个项目）、status（查 daemon 状态）、disable（关闭某项目的 daemon）等命令
merging-worktrees
axiomantic
"Use when merging parallel worktrees back together after parallel implementation, combining parallel development tracks, or unifying branches from dispatched parallel agents. Triggers: 'merge worktrees', 'combine parallel branches', 'integrate parallel work', 'all tracks complete', 'bring everything together'."
creating-issues-and-pull-requests
axiomantic
"Use when creating GitHub pull requests or issues with template compliance. Triggers: 'create a PR', 'open a pull request', 'file an issue', 'create issue', or invoked as delegate from finishing-a-development-branch Option 2. Discovers project templates, populates them from branch context, and creates via reliable gh CLI patterns."