Git & VCS
Git operations, commit helpers, branch management
dev.new
by kevinslin
Sync a repo to the latest master branch by checking out master and pulling from origin. Use when the user asks to refresh local state before new work.
dev.can-make-public
by kevinslin
Scan a repository and its git history for secrets, credentials, private keys, internal URLs, PII, and other sensitive artifacts before making it public. Use when a user asks if a repo is safe to open-source, requests a pre-publication audit, or wants to sanitize a repo for public release.
land
by kevinslin
Finalize a task by syncing status to the originating GitHub issue and, when in an AG directory, updating durable project docs (progress.md, memory.md, and related task tracking files).
dev.shortcuts
by kevinslin
Mandatory shortcut trigger and usage guidance. ALWAYS check if shortcut. Applies before responding to ANY coding or development request.
dev.conventional-commits
by kevinslin
Explain and apply the Conventional Commits specification for commit messages, including required format, types/scopes, breaking change notation, and examples. Use when asked to draft, validate, or review commit messages or when a repo wants Conventional Commits adoption.
dev.worktrees
by kevinslin
Standardize git worktree creation and management with all worktrees stored under ~/.worktrees/[repo]/[branch-name]. Use whenever running or planning git worktree commands (add/list/remove/prune), creating parallel checkouts, or setting up isolated branch workspaces.
artifact-management
by aj-geddes
Manage build artifacts, Docker images, and package registries. Configure artifact repositories, versioning, and distribution strategies.
calendar-scheduling
by openclaw
Schedule meetings, check availability, and manage calendars across Google, Outlook, and CalDAV. Routes to focused sub-skills for datetime resolution and calendar scheduling. Also available as temporal-cortex. Both listings install the same MCP server and share the same source code.
finishing-a-development-branch
by ed3dai
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
release
by m1heng
Publish a new release of the Feishu plugin. Use when the user asks to release, publish, or cut a new version.
starting-an-implementation-plan
by ed3dai
Use when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
maintaining-a-marketplace
by ed3dai
Use when creating, releasing, or maintaining a Claude Code Plugin Marketplace - covers marketplace.json schema, version management, release checklists, changelog conventions, and validation to prevent sync drift between plugin.json and marketplace.json
using-git-worktrees
by ed3dai
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
nav-install-multi-claude
by alekspetrov
Install Navigator multi-Claude workflow orchestration scripts. Auto-invokes when user says "install multi-Claude workflows", "set up multi-Claude", or "enable parallel execution".
multi-agent
by telagod
天罗秘典·多Agent协同。融合蚁群仿生设计，定义Agent角色、生命周期、信息素通信、任务分解、冲突解决。当需要多Agent并行协作时路由到此。
skill-sync
by jdrhyne
Sync Clawdbot skills between local installation and the shared skill repository. Use when asked to install, update, list, or push skills.
🔧 炼器秘典 · DevOps 能力中枢
by telagod
☠️ 一键为 Claude Code / Codex CLI 注入邪修人格与 40+ 安全工程秘典 npx code-abyss
clawdbot-release-check
by jdrhyne
Check for new clawdbot releases and notify once per new version.
云原生基础设施 · Infrastructure
by telagod
☠️ 一键为 Claude Code / Codex CLI 注入邪修人格与 40+ 安全工程秘典 npx code-abyss
claude-code-plugins
by melodic-software
"Read-only progressive-disclosure audit for agent-facing instruction markdown — grades every target against a three-tier load-cost model (always-loaded / invocation-loaded / on-demand) and classifies seven finding shapes in two lanes: split opportunities (oversize vs tier-calibrated Anthropic-prescribed caps, mixed-concerns, tier-mismatch — procedures, path-local, or sometimes-only content sitting in an always-loaded file) and disclosure-structure defects (blind-pointer lacking a when-to-read clause or read-vs-run intent, orphan-spoke, deep-nesting past one level, missing-toc on long references). Emits Tier 1/2/3 findings with per-shape treatment guidance; read-only, no edits applied. Use when: 'progressive disclosure', 'split this file', 'this file is too long', 'too much context', 'mixed concerns', 'hub and spoke', 'is my CLAUDE.md too big', 'audit context loading', 'what should always be loaded', or before splitting any instruction file — not for prose flavor (/docs-hygiene:compress), in-page noise (/docs-hygiene:audit-noise), whole-doc existence (/docs-hygiene:audit-derivability), or skill frontmatter QA (/skill-quality:check)."
claude-code-plugins
by melodic-software
"Iteratively reduce coupling at any altitude — documents, code modules, applications, or repositories: scan for change-transmitting dependencies typed against a coupling model, verify each finding, apply a budgeted batch of safe behavior-preserving reductions, and ledger structural candidates for design routing so repeated runs continue where the last stopped. Use when: 'reduce coupling', 'decouple', 'loosen coupling', 'too tightly coupled', 'high cohesion low coupling', 'break this dependency', 'dependency injection pass', 'externalize this config', 'connascence', 'coupling scan', 'these files always change together', 'stop copying between repos'. Skip when: reviewing a diff before merge (review tools), deep-designing one already-chosen boundary (/architecture:improve), general structural tidyings with no coupling focus (/code-tidying:tidy), or a docs noise/dedup pass with no cross-artifact coupling angle (docs-hygiene)."
render-deploy
by render-oss
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.
pr-creation
by TechDufus
"MUST be used when creating pull requests. Handles context gathering, title generation (conventional commit format), body formatting, and PR creation via GitHub CLI. Creates PRs as drafts by default. Triggers on: 'create PR', 'open PR', 'ready for review', 'push for PR', 'send for review'."
implement-plan
by steveclarke
Execute implementation plans incrementally with verification at each step. Works through numbered sections one at a time, sanity-checks assumptions against the codebase, and stops on inconsistencies. Use when implementing a pre-defined plan document. Triggers on "implement this plan", "execute step 3.1", "resume plan at section 4".