All authors
Claude Skills by wookiya1364
github.com/wookiya136416 skills0 installs0 views
- Gcleanmerge 후 원격에서 삭제된(upstream [gone]) 로컬 작업 브랜치를 안전하게 정리한다. 보호 브랜치(main·develop·stage)와 현재 브랜치는 절대 삭제하지 않고, 삭제 결과와 복구용 SHA를 출력한다.Votes: 0GitHub stars: 7
- CodegenTDD-first codegen for a scv/promote/<slug>/ plan. Verifies TESTS fail first (Red), then iteratively writes the minimum code to pass each case (Green). Hands off archive/PR/regression to /scv:work. Use whenever the user wants a plan implemented test-first — 'TDD', 'tests first', 'red-green' — not only when they type /scv:codegen. Never hand-roll the red/green loop instead of running this.Votes: 0GitHub stars: 7
- DeckTurn a markdown planning doc into a spec-grade 기획서 HTML — a buildless, self-contained document by default, or an on-screen slide presentation when you ask for one. Deterministic md→deck transform + a quality/gap lint; the raw markdown travels with it. Use whenever the user wants a planning document turned into something readable or presentable — 'make this a doc', '기획서로', 'slides' — not only when they type /scv:deck. Never hand-write the HTML.Votes: 0GitHub stars: 7
- HandoffDeclare that another repo needs corresponding development: write a handoff (+ decision + conversation) into the workspace root scv repo. Multi-repo (nested) only. Use whenever work in this repo implies a change another repo must make — not only when they type /scv:handoff. Never leave that dependency in prose; this command records it where the other repo will see it.Votes: 0GitHub stars: 7
- HelpShow SCV workflow + diagnose project + recommend next step. With an argument, talk through an idea OR search the archive for past work — SCV picks the right mode from your wording. Use whenever the user is thinking out loud about a change, asks what to do next, asks what SCV can do, or wants to find past work — not only when they type /scv:help. Never answer 'what should we work on' from memory; this command reads the project's real state and persists the conversation.Votes: 0GitHub stars: 7
- Install DepsDetect missing SCV system dependencies (git, gh, glab, curl, jq, ffmpeg, python3) and either show OS-specific install commands or run them. graphify (Claude Code skill) is detected separately and links to its install guide. Use whenever a command reports a missing external tool, or the user asks what SCV needs installed — not only when they type /scv:install-deps.Votes: 0GitHub stars: 7
- PromoteRefine scv/raw/ material into a scv/promote/<YYYYMMDD>-<author>-<slug>/ folder with PLAN.md + TESTS.md. Optionally updates the docs knowledge graph. Interactive; no files written without user approval. Use whenever the user wants a change planned, specced, or broken down before implementation — 'plan this', 'write a spec', 'what should we build' — not only when they type /scv:promote. Never draft PLAN.md or TESTS.md yourself instead of running this; a plan written by hand skips the raw-materi...Votes: 0GitHub stars: 7
- RegressionRun accumulated regression across scv/archive/**/TESTS.md (and optionally promote/) with supersede/obsolete skip graph. On failure, triage the failed slugs via AskUserQuestion — one question per slug (regression / obsolete / flaky), the recommended verdict first, four slugs per call. Use whenever the user asks whether past features still pass, or before archiving anything — 'run the tests', 'is anything broken' — not only when they type /scv:regression. Never assemble the archived test suite ...Votes: 0GitHub stars: 7
- ReportPost a phase/status report to the team channel per REPORTING.md. Reads .env NOTIFIER_PROVIDER (slack|discord) and uploads E2E artifacts from test-results/. Use whenever the user asks to tell the team, post an update, or share progress — not only when they type /scv:report. Never compose the message by hand; this one follows REPORTING.md and attaches the real artifacts.Votes: 0GitHub stars: 7
- RoutineExecute one maintenance routine defined in scv/routines/<name>.md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when they type /scv:routine.Votes: 0GitHub stars: 7
- Set ModelsChoose a model policy and apply it to every SCV command's frontmatter. Persists the choice in scv/scv_settings.json so /scv:sync can reapply it after a plugin update. The shipped default is the session model — no per-command model selection until you turn one on. Use whenever the user wants to change which model SCV commands run on — not only when they type /scv:set-models.Votes: 0GitHub stars: 7
- StatusShow raw changes since last index + list of active promote plans. Use whenever the user asks what is in flight, what changed, or where things stand — not only when they type /scv:status. Never summarize project state from memory; this command reads it.Votes: 0GitHub stars: 7
- SyncSync the SCV template into this project, honoring frontmatter merge_policy. PROJECT:LOCAL blocks are always preserved. Use whenever the user updated the plugin, asks to refresh SCV's own files, or asks whether code has drifted from an active plan — not only when they type /scv:sync.Votes: 0GitHub stars: 7
- UpdateCheck installed SCV plugin version vs latest release, and guide the user through /plugin marketplace update + /reload-plugins. Read-only — does not modify project files. (v0.11.2+) Use whenever the user asks whether SCV is current or how to update it — not only when they type /scv:update.Votes: 0GitHub stars: 7
- WorkImplement a scv/promote/<slug>/ plan. Reads PLAN.md + TESTS.md, proposes/loads Related Documents as needed, runs the tests, and optionally archives on success. Use whenever the user wants an existing plan implemented — 'build it', 'implement the plan', 'let's do it' — not only when they type /scv:work. Never implement a promote plan by editing files directly; this command loads the plan, runs its TESTS, and records what actually changed.Votes: 0GitHub stars: 7
- WorkspaceSet up or change this repo's place in a multi-repo SCV workspace: join an umbrella as a child, create an umbrella (root), check status, or detach. Friendly — no long flags to remember. Use whenever the user asks how this repo relates to sibling repos, or wants to join, create, or leave a multi-repo workspace — not only when they type /scv:workspace.Votes: 0GitHub stars: 7