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

refine

Review a work session to identify slow steps, failures, missing information, and useful patterns. Then make concise, evidence-based updates to relevant documentation so confirmed lessons can help with future sessions.

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

원문원문 설명 보기

End-of-session reflection. Reviews friction encountered during the session and proposes updates to docs/ to capture lessons learned.

windmill-labs/windmill스타 18,276(GitHub 18,276 + cccskills 0)

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Recording a confirmed codebase pattern in project docs
  • Adding a missing validation check discovered during a session
  • Correcting documentation that led to a failed or repeated step

포함된 파일(1)

  • SKILL.md1.6 KB

SKILL.md(원문)

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

Refine Skill

Reflect on the current session and update documentation with lessons learned.

Instructions

  1. Identify friction: Review what happened in this session:

    • Run git diff main...HEAD --stat to see what files were touched
    • Think about: what was slow, what failed, what required multiple attempts, what information was missing or hard to find
  2. Read current docs: Read the docs that were relevant to this session:

    • docs/validation.md
    • docs/enterprise.md
    • Any skills that were invoked
  3. Propose updates: For each piece of friction, decide if it warrants a doc update:

    • Missing knowledge: Information you had to discover that should be documented
    • Wrong guidance: Instructions that led you astray
    • Missing validation rule: A check that should be in the validation matrix
    • New pattern: A codebase pattern worth capturing for next time
  4. Apply updates: Edit the relevant docs/ files. Keep changes minimal and specific — add only what would have saved time this session.

  5. Report: Summarize what was added/changed and why.

Rules

  • Only add knowledge confirmed by this session — no speculative additions
  • Keep docs concise — add a line or two, not a paragraph
  • If a whole new doc is needed, create it in docs/ and add a pointer in CLAUDE.md
  • Don't update skills unless a coding pattern was genuinely wrong
  • Don't add things Claude already knows — only Windmill-specific knowledge

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Plan the code changes needed to add a TriggerCrud-based trigger to Windmill. The checklist covers backend, database, API, CLI, frontend, capture, and validation work so the new trigger can be managed across the product.

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

  • Add a Kafka, GCP, or Azure style trigger to Windmill
  • Find all product areas affected by a new trigger kind
  • Review implementation and validation steps before a trigger PR
windmill-labs/windmill1.8만2026년 10월 26일 업데이트

ai-chat

무료

Improve Windmill’s AI chat by reviewing its tools, prompts, result shapes, and context usage. The guidance helps place shared instructions where chat and CLI can use them, reduce repeated token costs, and compare behavior before and after changes with A/B evaluations.

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

  • Edit Windmill chat tools or system prompts
  • Reduce chat context window usage
  • Benchmark a chat behavior change
windmill-labs/windmill1.8만2026년 10월 26일 업데이트

ai-evals

무료

Create and run black-box benchmarks for Windmill AI generation modes such as flows, apps, scripts, CLI, and global requests. Each case exercises the production path, checks hard requirements, and uses an LLM judge to assess user-facing behavior before and after changes.

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

  • Adding a benchmark case for an AI mode
  • Comparing AI chat behavior before and after a change
  • Checking copilot changes with realistic requests
windmill-labs/windmill1.8만2026년 10월 26일 업데이트

Use this reference to work with Windmill resources from the command line, including scripts, flows, datatables, and workspace settings. It also covers listing jobs, inspecting details and logs, retrieving results, and rerunning or restarting executions when investigating failures.

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

  • Inspecting a failed job and its logs
  • Reviewing recent runs and retrieving job results
  • Managing scripts and flows from the command line
windmill-labs/windmill1.8만2026년 10월 26일 업데이트

Use this skill to shape modules with small interfaces and substantial behavior behind them. It helps you decide where a seam belongs, reduce complexity exposed to callers, and make code easier to test and maintain.

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

  • Designing a module interface
  • Finding places to simplify a module
  • Choosing where behavior should vary
windmill-labs/windmill1.8만2026년 10월 26일 업데이트

commit

무료

Use this skill to review pending changes, select only the relevant files for staging, and create a focused Git commit. It formats the single-line message with a Conventional Commits type such as feat, fix, or docs, and checks the resulting status.

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

  • Committing a new feature
  • Recording a bug fix
  • Committing documentation changes
windmill-labs/windmill1.8만2026년 10월 26일 업데이트

windmill-labs의 스킬 모두 보기

이 스킬의 문제 신고