Orchestrates GitHub issues through the full SDLC pipeline to merged pull requests.
npx skills add https://github.com/Dozyboy/VSF --skill hs-vibe-dozyboy
Please help me install this Agent Skill. Skill: hs:vibe Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/disabled-skills/vibe Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-vibe-dozyboy
--ship flag, merges the PR per branch protection rules and watches target-branch CI, spawning follow-up fixes for repo-fixable failures. - Gate-respecting autonomy: Routes through existing plan-approval, ship, and protected-branch gates without bypassing or weakening them, and records external blockers instead of hiding failures. - Use Case: Paste a GitHub issue URL and receive a reviewed, labeled, ready-to-ship PR — or a merged commit with green CI — without hand-driving each pipeline step. ## Quick Start Run the vibe command with a GitHub issue URL, optionally adding the --ship flag to merge and converge CI after the PR is reviewed and approved.High-intent search queries and answers about installing and using this skill.
Run the vibe command with the issue URL and the --ship flag. It creates a worktree, validates and red-teams a plan, implements via the feature or bugfix route, ships the PR, resolves review findings, merges, and watches target-branch CI until green.
Invoke the command with just the issue URL and no --ship flag. The pipeline stops after the PR is reviewed, fixed, replied to, and labeled ready to ship stable or ready to ship beta.
No. The plan-approval gate and the ship gate requiring review-PASS, verification-PASS, and human approval remain enforced. The orchestrator supplies the artifacts those gates require and pauses at the same human checkpoints as any autonomous run.
The pipeline inspects the failed run logs, branches a follow-up fix from the target branch, applies a fix with the exact error evidence, re-ships, re-reviews, and re-watches CI. It stops at green CI, an external blocker, or three failed attempts on the same blocker.
Yes. Natural-language input is treated as a feature request, but a GitHub issue is created only after the plan passes validation and red-teaming. An existing issue URL is always treated as the source of truth and never duplicated.
Avoid it for single SDLC steps — invoke the individual plan, cook, fix, code-review, ship, or review-pr skills directly instead. It is designed for carrying an issue end-to-end, not for isolated tasks.
PelekeDraft structured GitHub issues with titles, descriptions, and acceptance criteria.
Devin-AXISCompare Sentry releases and time windows to detect regressions and user-impact changes.
acedergrenPlan, implement, validate, and commit software changes through autonomous sub-agents.
jikig-aiExecute planning, implementation, review, QA, and ship stages for Git projects.