gitgitWi/council-flow
Skill Claude CodeCodex
Tear down a finished task's transient resources — kill the dev server / e2e / Playwright processes it started, remove the git worktree, prune stale preview deployments (keeping the last N), and note the cleanup on the parent issue. Use once a task's PR is merged (or abandoned) and you want the workspace and running…
gitgitWi/council-flow
Skill Claude CodeCodex
Write the base material for a code review — a "review brief" for a pull request that the USER feeds to their own external agent(s) to post review/comments on GitHub. This skill does NOT perform the review itself and does NOT post comments; it prepares the document a reviewer works from. The flow agent gathers the…
gitgitWi/council-flow
Skill Claude CodeCodex
The fast commit → push → open-or-update-PR loop, with the standard rules baked in so they never need retyping. Use whenever the user says "commit", "commit and push", "push", "PR 올려", "PR 갱신", "update the PR", or wants the current changes shipped to a pull request. Splits work into atomic Conventional Commits, pushes…
gitgitWi/council-flow
Skill Claude CodeCodex
Push the task branch and open a Korean pull request, then ask the user whether to run flow:code-review-brief and, on confirm, run it inline for the new PR. Use this whenever development for a flow task is done and the branch is ready for review. Even when the user says "just open a PR", finish by offering the…
gitgitWi/council-flow
Skill Claude CodeCodex
Execute the implementation phase of the flow workflow — read tasks.md, pick the next unchecked behavior, write a failing test (when TDD applies), implement until green, commit atomically with conventional commits, and check the box. Use this for any actual code change in a flow task, whether or not a plan exists. Even…
gitgitWi/council-flow
Skill Claude CodeCodex
The single entry point for any flow task — it both frames the work AND sets up the workspace, so there is nothing to call before it. Start here for every new piece of work — a feature, bug fix, debug, chore, refactor, or research question — even a one-line "fix X" or "이거 작업하자". Kickoff figures out the task type…
gitgitWi/council-flow
Skill Claude CodeCodex
Run the full flow workflow end-to-end — kickoff (framing + setup) → optional research → plan (with optional multi-LLM brainstorming) → develop → deploy → optional cleanup — based on a single task goal from the user. Use this when the user wants to hand off a complete task and let the workflow run, rather than driving…
gitgitWi/council-flow
Skill Claude CodeCodex
Produce a short, visual plan.md (goal + approach + a Mermaid diagram of the direction) and a concise checklist tasks.md for an upcoming task. Use this whenever the user is about to start a non-trivial change — a feature, multi-file fix, refactor — before any code is written. Even if the user just says "let's start"…
gitgitWi/council-flow
Skill Claude CodeCodex
The express entry for a task the user judges trivial — skip framing/research/plan and go straight toward develop, but only after a fast sanity check. Use when the user says the work is small and wants speed ("그냥 바로 해줘", "간단한 거니까 바로", "바로 develop", "just do it", "quick fix", "skip the planning"). Quick applies a…
gitgitWi/council-flow
Skill Claude CodeCodex
Investigate codebase context, related projects, and external sources for a task that is large or unfamiliar enough that planning blind would waste effort. Use this when the task crosses modules, touches a subsystem the user has not worked on recently, or depends on external APIs / libraries whose current shape…
gitgitWi/council-flow
Skill Claude CodeCodex
Triage and address code-review feedback on a pull request. Fetches ALL feedback types — review summaries, inline review comments, review threads/discussions, and general PR conversation comments — then assesses each for validity and priority, writes a fix plan, and (after the user approves) applies the fixes as atomic…