Initialize repositories into the Anti-Vibe Coding methodology with scaffolding and CI files.
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill init-luyzkk
Please help me install this Agent Skill. Skill: init Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/init Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill init-luyzkk
This Skill prevents chaotic “vibe coding” by onboarding a project into the Anti-Vibe Coding methodology, setting up the required guardrails, harness structure, and migration/rollback safety for first-time adoption or cross-version upgrades.
Run the init from a shell using the plugin CLI: call the provided init-cli script with the project directory so the dispatcher can generate the full scaffold correctly.
High-intent search queries and answers about installing and using this skill.
Anti-Vibe Coding prevents chaotic AI code generation by scaffolding project docs, installing CI files, and registering rules to establish consistent guardrails. This methodology onboards repositories with a structured harness, ensuring disciplined development through verified initialization and safety-first migrations.
To initialize project scaffolding, run the provided init-cli script from a shell using the plugin CLI with your project directory. The dispatcher generates the full scaffold, runs idempotent detection steps, wires CLAUDE.md/AGENTS.md, and executes final harness validation to ensure coherent setup.
Yes, the scaffolding migration supports legacy v5.x repositories with dry-run, refresh, additive-merge, and rollback controls. It detects existing v5.x state and performs idempotent migration steps, ensuring safe onboarding with reversible rollback support and backup creation for CLAUDE.md transformations.
CLAUDE.md and AGENTS.md files undergo safety-first handling during onboarding through guarded, user-approval-aware merges and transformations. The process creates backups, supports reversible rollback, and optionally injects a delivery-loop section into the AGENTS workflow for teams requiring it.
Yes, dry-run mode allows you to preview scaffolding changes before modifying your repository. The initialization pipeline executes detection and migration steps idempotently, letting you validate the generated structure, CI files, and planned rule registrations before committing any transformations.
Automated scaffolding detects greenfield versus legacy v5.x state to apply appropriate structures, but limitations arise when existing repository configurations conflict with the harness validation. Users must review guarded CLAUDE.md merges and approve transformations, as the safety-first approach requires user approval for irreversible structural changes.
epicrunzeScaffold a project-scoped .jarvis data directory with identity, memories, and journal storage.
kwam1naScaffold agent-ready repositories with onboarding docs, validation maps, and CI wiring.
shiroinockCoordinate TDD task orchestration from GitHub issue selection to PR completion.
X-School-AcademyInitialize a coding project from a requirements file with Git and optional GitHub setup.
