본문으로 건너뛰기
cccskills
무료GitHub에 공개

decide

Work through design or implementation choices one at a time, with concise context and clear alternatives. You can also review completed code change by change, recording decisions, approvals, and requested revisions in a final table.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Walk the user through design or implementation decisions one at a time, or review completed code one change at a time. Use when the user says "walk me through each decision", "let's decide together", "help me work through these choices", "walk me through what you did", or "QA step by step". Present concise context, mutually exclusive options, log each answer, and finish with a summary.

설치 방법 보기

이럴 때 유용합니다

  • Compare design choices one decision at a time
  • Resolve implementation choices with recorded answers
  • Review completed code in logical steps
  • Collect approvals and revision requests for changes

포함된 파일(2)

  • SKILL.md2.7 KB
  • agents/openai.yaml196 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Decide

Prepare

Before a design walkthrough, inspect the relevant code and record concrete bugs, inconsistencies, and decision points in plans/<YYYYMMDD>-<topic>.md or the appropriate app-scoped plans/ directory. Preserve existing edits; never discard speculative or user-authored work without explicit approval.

Order decisions by dependency and leverage, not document order.

Decision walkthrough

For each decision:

  1. Show ## Decision N: <title>.
  2. Give two to four sentences of context grounded in real files or functions.
  3. State the trade-off in one sentence.
  4. Ask exactly one interactive question with two to four mutually exclusive options.
    • Use ask_user when available. In Codex Plan mode, use request_user_input when that is the exposed interactive question tool.
    • Never substitute a plain-text question when repository instructions require an interactive overlay.
    • Keep labels to five words or fewer.
    • Put the recommendation first and suffix its label with (Recommended).
    • Explain each option and its trade-off in one sentence.
    • Do not add an Other option when the client adds one automatically.
  5. After the answer, write Logged: <decision>. and continue.

If the user acknowledges an issue without choosing, log the recommended choice and say they can correct the assumption.

At the end, provide a | # | Decision | Choice | table and offer to turn the audit into an implementation plan. Do not write implementation code during the decision walkthrough.

QA walkthrough

Use this mode when the user wants to review existing code step by step.

  1. Identify the review unit: a commit, staged diff, PR, or explicit file set.
  2. Break it into logical steps in dependency order.
  3. Show one step per turn with:
    • ## Step N: <title>
    • One or two sentences explaining what changed and why
    • A focused real-code excerpt with file and line references
    • One interactive verdict question: Looks good, next step (Recommended), Push back, change this, and, only for non-trivial code, Pause, explain more
  4. Wait for the verdict before showing the next step.
  5. Log approvals, collect requested changes, and finish with a | # | Step | Verdict | table.

If a step reveals a genuine design fork, pause the QA walkthrough and offer to switch to decision mode for that fork.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

10x

무료

Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Find unused Superset features worth exploring
  • Set up scheduled agent tasks
  • Start parallel work in separate workspaces
superset-sh/superset1.5만2026년 10월 18일 업데이트

automate

무료

Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Scheduling a daily or weekly agent task
  • Starting agent work when a GitHub pull request opens
  • Triggering tasks from selected Slack reactions
superset-sh/superset1.5만2026년 10월 18일 업데이트

browser

무료

Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Preview a locally running web app
  • Capture screenshots of a page
  • Inspect console errors
superset-sh/superset1.5만2026년 10월 18일 업데이트

Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choose Stripe products for payments or recurring billing
  • Implement Checkout or invoice flows
  • Investigate Stripe code that compiles but behaves incorrectly
superset-sh/superset1.5만2026년 10월 18일 업데이트

Verify desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reproducing reported bugs in the running app
  • Comparing UI behavior before and after a fix
  • Checking state across navigation and reopening
superset-sh/superset1.5만2026년 10월 18일 업데이트

ci-triage

무료

Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating failed PR checks
  • Separating intermittent test failures from code defects
  • Checking whether the base branch already fails
superset-sh/superset1.5만2026년 10월 18일 업데이트

superset-sh의 스킬 모두 보기

이 스킬의 문제 신고