Audit task registry metadata and summarize flows across multiple worktrees.
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-task
Please help me install this Agent Skill. Skill: vibe-task Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-task Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-task
Provides a clear, semantically informed overview of flows and tasks across multiple worktrees and audits task registry metadata so users know which local scene to resume and where data quality gaps exist.
Ask the assistant to inspect all worktrees using the project's CLI outputs for task status and flow show, summarize each worktree's current task and state, and recommend which flow or task to resume next.
High-intent search queries and answers about installing and using this skill.
To audit task registry metadata, the Skill parses CLI outputs to identify missing or inconsistent fields without directly modifying JSON or SQLite sources. It surfaces capability gaps and only proposes repairs when atomic shell commands exist and the user confirms them.
The safest way to fix task registry metadata is to enforce strict boundaries by obtaining all evidence via the project's CLI. Avoid direct modification of JSON or SQLite sources, and only propose or run fixes when corresponding atomic CLI commands exist and the user confirms them.
Yes, you can audit task registry metadata in a repository with multiple worktrees by running the project's CLI commands for task status and flow show. The Skill parses these CLI outputs to evaluate flow states and registry consistency without directly reading underlying JSON or SQLite databases.
You should avoid directly modifying JSON or SQLite sources during a task audit to maintain data integrity and prevent corruption. The Skill enforces a shell-grounded workflow, ensuring all evidence is obtained via the project's CLI and fixes only run using confirmed atomic commands.
A limitation of using CLI output parsing for cross-worktree flow overviews is that repairs are constrained to scenarios where atomic shell commands exist. The Skill cannot fix metadata gaps if corresponding CLI commands are unavailable, and it strictly avoids directly modifying underlying data sources.
lucidashAutomate Git worktree creation, switching, listing, and cleanup via CLI.
JHaugaardRead handoff documents in .docs/ to display project workflow progress.
erclxRemove merged git worktrees and prune associated local branches.
fcakyonQuery Supabase databases to list tables, inspect schemas, and explore relationships.
