jacobcy
34 verified skills130 total stars
vibe-integrate
Use when the user wants to assess, unblock, and merge PRs. This is a human-facing convergence entrypoint that explains integration status and guides decisions, not an automated merge workflow.
testing5
vibe-team-review
Use when the user wants a comprehensive review using the multi-agent team workflow. Applies to PRs, code changes, architecture decisions, and any task requiring team-based analysis.
development5
vibe-save
Use when the user wants to save session context. This is a human-facing session handoff entrypoint that preserves work state via vibe3 handoff, not an automated persistence workflow.
testing5
vibe-commit
Use when the user wants to classify dirty changes, create serial commits, split work into one PR or multiple PRs, and prepare publication from the correct flow without handling merge or post-merge closure.
tools5
vibe-done
Use when the current human-collaboration flow has reached terminal PR state and the user wants to do final closeout. Confirm PR outcome, close owned issues, check for follow-up needs, delete resources, and switch back to main. Do not use for code changes or abandoned work.
development5
vibe-closeout
Use when manager has signaled flow terminal state cleanup via handoff indicate. Reads cleanup instructions and executes FlowCleanupService. Do not use for code changes or PR creation.
development5
vibe-project-check
Use after `vibe init` to verify project configuration completeness. Interactively prompts user to fill missing items. Orchestrates existing commands without adding Python code. Do not use for system-level installation issues (use vibe-onboard instead).
development5
vibe-check
Use for deep inspection of single flow when automated processes fail. Human intervention for complex flow/task binding issues, runtime state inconsistencies, and manual diagnosis. Do not use for routine monitoring (use vibe3 task status) or system-level debugging (use vibe-debug-serve).
development5
vibe-instruction
Use when you need an overview of the Vibe Center project, its implementations (vibe2 shell and vibe3 python), the available commands, and the standard development workflow. This is the meta-skill that orients any agent to the project.
development5
vibe-new
Use when starting or switching to a new human-collaboration task. Confirm the target issue, bootstrap the corresponding dev/issue flow scene, and hand off to the chosen implementation workflow. Do not use for resuming an existing branch; use vibe-continue instead.
development5
vibe-issue
Use when the user wants to create or refine a GitHub issue. This is a human-facing intake entrypoint, not an automated workflow.
testing5
vibe-orchestra
Use when the user wants heartbeat-style governance over the issue pool. inspect running issues, judge which issue is worth starting next, backfill assignee-triggered candidates, and propose non-state label or routing actions. Do not use for single-flow execution governance, coding, or implementation work.
development5
vibe-review-code
Use when the user wants a structured code review for local or PR-bound source changes, asks for a pre-PR implementation audit, or wants fixes validated against code review feedback. Do not use for docs-only review, concept governance, PR publishing, merging, or CI debugging.
development5
vibe-onboard
Use after `scripts/install.sh` to guide users through system setup, dependency checks, and core feature introduction. Interactive onboarding for new users. Delegates diagnostics to `vibe doctor` and `vibe keys check`. Do not use for project-level configuration (use vibe-project-check instead).
testing5
vibe-task
Use for handling blocked and RFC issues, making decisions that may form ADRs (Architecture Decision Records). Processes problem issues requiring human judgment, dependency resolution, and architectural decisions. Do not use for routine issue monitoring (use vibe-orchestra) or roadmap planning (use vibe-roadmap).
testing5
vibe-roadmap
Use when the user wants project-level roadmap planning, version goals, backlog triage, governance suggest review, or issue placement decisions. Triggered by "vibe roadmap", "/vibe-roadmap", "版本规划", "roadmap 审查", "消化 governance suggest", "下一个版本做什么", or "这个 issue 放哪一版". Do not use for assignee pool governance (use vibe-orchestra) or single-flow execution.
development5
vibe-debug-serve
Use when checking orchestra service health, viewing serve running status, debugging vibe3 serve (orchestra server), checking whether a new serve debugging round is ready, inspecting agent execution logs in temp/logs/, diagnosing governance or manager chain failures, or identifying bugs in the heartbeat/dispatch pipeline. Triggered by "serve status", "orchestra service running", "FailedGate", "heartbeat", "serve health". Do not use for flow/task metadata repair (use vibe-check) or issue pool governance (use vibe-orchestra).
development5
vibe-continue
Use when the user wants to resume work on an existing branch or flow. This is a human-facing resume entrypoint that explains current context and suggests next steps, not an automated bootstrap workflow.
testing5
vibe-boundary-check
在开发过程中定期检查代码指标是否在治理边界内
testing3
vibe-review-docs
Use when the user wants to review documentation changes, audit entry files or standards docs, check changelog quality, inspect concept drift in docs, or says "review docs" / "review documentation". Do not use for source-code implementation review.
development3
vibe-skill-audit
Use when the user wants to create, update, review, or audit a repo-local Vibe skill under `skills/`, mentions "/vibe-skill-audit", "vibe-skill", "vibe skill", "创建 skill", "审查 skill", "skill 文案", or "自动匹配语义", or needs a Vibe-specific wrapper around `skill-creator` rather than a generic cross-project skill workflow.
testing3
vibe-orchestrator
统一编排 Vibe Guard 流程，作为所有改代码动作的主路由。
tools3
vibe-redundancy-audit
Use when the user wants to find suspicious redundant business logic, repeated implementation patterns, stale compatibility paths, or low-quality code that should be reviewed for consolidation, reuse, or retirement. Do not use for automatic cleanup or direct code deletion.
development3
vibe-scope-gate
在新 flow 启动时检查新功能是否在项目范围内
tools3
vibe-rules-enforcer
在 review 阶段执行全量合规检查，生成 PR 合规报告。
tools3
vibe-review-pr
Use only in Claude Code environments with Agent Teams enabled when the user wants a comprehensive PR review using the multi-agent team workflow.
development3
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
tools2
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
tools2
vibe-rules
Use when rules files change, when checking for duplicate or conflicting rules across ~/.claude/rules/common/, .claude/rules/, .agent/rules/, and CLAUDE.md, or when an agent has created new rules that may overlap with existing ones. Do not use for skill authoring or flow governance.
development2
vibe-skills-manager
Use when installed skills are messy across IDEs, the user is unsure which skills exist globally vs project-level, needs to sync, clean, or recommend installed skills, is setting up a new worktree, or mentions "/vibe-skills-manager". Do not use for authoring or reviewing `skills/vibe-*` content.
content-media2
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
tools2
vibe-audit
Use when evaluating whether a project should continue, be refactored, rebuilt, forked, or abandoned — for both own projects and external/third-party codebases
development2
vibe-drift
定期检测项目是否偏离初衷。
tools2
vibe-test-runner
代码修改后自动执行四层验证（Serena 影响分析 + Lint + 测试 + Review Gate），失败时循环修复（最多 3 轮）
development2