Git 与版本控制
Git 操作、提交助手与分支管理
cats-effect-io
alexandru
Scala functional programming with Cats Effect IO and typeclasses. Use for wrapping side effects, modeling purity, choosing Sync/Async/Temporal/Concurrent, handling blocking I/O, and composing resources, fibers, and concurrency safely.
branch-cleanup
strikersam
Delete remote and local branches that have been merged into master. Run after every merge to keep the repo to master-only. Supports both git-push deletion and GitHub API deletion (when git push --delete returns 403 due to proxy restrictions).
wrap-up
strikersam
Session closing ritual with learning capture. Run at the end of every coding session. 5 steps: changes audit, quality check, learning capture, next session planning, summary.
Skill: ticket-to-pr
strikersam
→ scope-guard: to stay focused
repo-memory-updater
strikersam
Keep CLAUDE.md files and .claude/state/ in sync with the current repo reality. Use after significant structural changes, after adding risky modules, or when CLAUDE.md feels stale.
smart-commit
strikersam
Quality gates + conventional commits. Run tests, lint, and typecheck before committing. Format the commit message as a conventional commit. Blocks on failure.
pro-workflow
strikersam
Core AI coding workflow. Orchestrates 8 patterns: Scout → Plan → Implement → Review, with smart commits, session rituals, and continuous learning capture. This is the master skill — invoke it at the start of any non-trivial task.
parallel-worktrees
strikersam
Git worktree setup for zero dead time. Work on multiple branches simultaneously without switching branches or stashing. Ideal for running tests on main while implementing on a feature branch.
Skill: resource-panel
strikersam
summarise.sh — auto-generate panel from git state
repowise-intelligence
strikersam
Implements codebase intelligence layers similar to repowise-dev/repowise. Provides dependency graph, git history, auto-generated documentation, and architectural decisions intelligence for AI agents.
session-handoff
strikersam
Write structured resume documentation for the next session. Captures state, context, and next actions so any AI or developer can continue without archaeology.
session-planning
strikersam
Mandatory planning workflow for all AI agents — decompose tasks before execution
altinity-expert-clickhouse-storage
Altinity
Diagnose ClickHouse disk usage, compression efficiency, part sizes, and storage bottlenecks. Use for disk space issues and slow IO.
dead-code-scanner
Terryc21
'Find unused code after refactors or as ongoing hygiene. Two modes: quick (post-refactor, recent changes) and full (entire codebase). Triggers: "find dead code", "find unused code", "cleanup unused", "dead code scan", "code hygiene".'
explain
Terryc21
'Deep-dive explanation of how a specific file, feature, or data flow works. Triggers: "explain", "how does X work", "walk me through", "what does this do".'
review-changes
Terryc21
'Pre-commit review of staged/unstaged changes for bugs, security, performance, and missing tests. Scoped to changed files only. Triggers: "review changes", "review my code", "check before commit", "pre-commit review".'
gitlab-cli-skills
vince-winkintel
Comprehensive GitLab CLI (glab) command reference and workflows for all GitLab operations via terminal. Use when user mentions GitLab CLI, glab commands, GitLab automation, MR/issue management via CLI, CI/CD pipeline commands, repo operations, authentication setup, or any GitLab terminal operations. Routes to specialized sub-skills for auth, CI, MRs, issues, releases, repos, and 30+ other glab commands. Triggers on glab, GitLab CLI, GitLab commands, GitLab terminal, GitLab automation.
rss-digest
odysseus0
"Agentic RSS digest using the feed CLI. Fetch, triage, and summarize RSS feeds to surface high-signal posts. Use when: (1) reading RSS feeds or catching up on news, (2) user asks for a digest, roundup, or summary of recent posts, (3) user asks what's new or interesting today, (4) user mentions feed, RSS, or blogs."
agent-changelog
petekp
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
history-analyzer
lis186
Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.
proposal-review
petekp
Facilitate methodical review of proposals (technical designs, product specs, feature requests). Use when asked to "review this proposal", "give feedback on this doc", "help me review this RFC", or when presented with a document that needs structured feedback. Handles markdown files, GitHub gists/issues/PRs, and other text formats. Chunks proposals intelligently, predicts reviewer reactions, and produces feedback adapted to the proposal's format.
consolidate-task-prs
osdlc
Collapse every open single-task-file PR — each carrying one new draft task file under docs/planning/tasks/ — into a single consolidation PR, deduping the folded tasks against the present task list, then close the superseded PRs and delete their branches. Explicit cleanup only, never auto-invoked: run it to fold an accumulation of one-task-each PRs back into one reviewable PR.
duplication-scan
osdlc
Run a deep, evidence-backed scan of a repository for duplication (the same logic, contract, configuration or infrastructure implemented more than once) and modularization opportunities (code to extract, split, move, or re-wire in the right dependency direction), as an orchestrated adversarial loop: Prospector agents generate candidates, Adversary agents with no shared context try to falsify them, an Arbiter adjudicates against a fixed rubric, and the loop exits only on measured convergence. Read-only on the source tree; writes a map, a ledger, a decision report, a round log and a one-PR pilot plan under a work directory. Use when asked to find duplicated code, copy-pasted wrappers, parallel implementations, drifted copies, "shared package" candidates, wrong-tier packages, god packages, or to audit a monorepo's modularization; when a user says "what should be extracted", "where are we repeating ourselves", or "is this package in the right place".
capability-review
osdlc
Review existing Capability entities for accuracy against the code they anchor: do the locations still realize the Statement, do kind, audience and state match the shared rubric, do parent_key and related still resolve, does the body describe what the code does. Runs sdlc capability coverage and sdlc capability graph read-only, dispatches one read-only sub-agent per capability, and prints a report. With --fix it also corrects frontmatter through sdlc capability update and stamps last_reviewed; with --rewrite it also rewrites drifted body sections; both open a PR. Invoke after a mapping run, after a refactor that moved packages, or when the System page's capability view looks wrong. Usage: /sdlc:capability-review <dir C-NNNN all> [--fix] [--rewrite] [--auto].