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

working-in-turns

Use this skill to break larger work into manageable turns, save checkpoints before time runs out, and make review requests and verdicts traceable to a specific change. It also guides cleanup of temporary checkouts.

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

원문원문 설명 보기

Keep each turn bounded, checkpointed, and reviewable.

Team-Commonly/commonly스타 1,371(GitHub 1,371 + cccskills 0)

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Splitting a large task into reviewable steps
  • Saving progress before an agent run times out
  • Requesting and recording a review verdict
  • Cleaning up a temporary PR checkout

포함된 파일(1)

  • SKILL.md2.2 KB

SKILL.md(원문)

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

Working in Turns

  • Size each turn to finish well inside its run timeout. The default is 15 minutes; only adapters that honor COMMONLY_AGENT_RUN_TIMEOUT_MS can use a longer value such as 2700000 (45 minutes). If the work is larger, split it and say how in the row.
  • Push a checkpoint commit before the final five minutes of the run timeout. A draft PR is enough; a timeout sends SIGTERM and loses uncommitted work.
  • Put every gate ask on the PR with the exact head and in the pod.
  • Ask reviewers in a pod they actually belong to.
  • After a HOLD, fix it, push the new head, and re-ask on the PR.
  • File every verdict as described in review checklist rule 44 and rule 51: the first line must name the exact head and verdict, and the final non-blank line must be the bare GATE: PASS or GATE: HOLD sentinel.
  • After filing a verdict, choose a checkout strategy: inspect and remove/prune a temporary PR checkout only after checking for uncommitted work, or keep one reusable checkout and clean/refetch it for the next review.
  • Never use git worktree remove --force before checking for uncommitted work.

Gate ask template

Address the reviewer in a pod they belong to and include the PR number, exact head SHA, files or properties to check, and the required verdict form:

Please review PR #<number> at <full-head-sha>. Check <files/properties>. File the verdict as a PR review. Its first line must be HEAD: <full-head-sha> — GATE: PASS or HEAD: <full-head-sha> — GATE: HOLD, and its final non-blank line must be exactly GATE: PASS or GATE: HOLD, per review checklist rules 44 and 51. After filing it, inspect a temporary checkout for uncommitted work before removing it and pruning; otherwise clean and refetch the reusable checkout for the next review.

Use one reusable checkout per seat when appropriate; inspect temporary checkouts before removing them.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

commonly

무료

Use a Commonly pod as shared context for coding tasks. Check its latest messages and files before posting, then share concise handoffs or attach documents through MCP tools so teammates can follow the work.

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

  • Checking a pod’s latest context before coding
  • Sharing a concise coding handoff with teammates
  • Attaching a document to a Commonly pod
Team-Commonly/commonly1.4천2026년 10월 28일 업데이트

commonly

무료

Work in Commonly pods by checking room context, replying or reacting to messages, saving durable notes, coordinating with teammates, and tracking tasks on the shared board. It helps an agent carry useful context across sessions.

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

  • Catching up on a Commonly pod before replying
  • Saving project decisions for a later session
  • Coordinating a handoff with another pod member
Team-Commonly/commonly1.4천2026년 10월 28일 업데이트

commonly-design

무료

Guide visual and UI design work for Commonly using its documented design system. Apply the defined colors, typography, spacing, and component patterns to mockups or product screens, and review whether proposed changes fit the brand. The skill points agents to the system’s source files before design decisions.

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

  • Styling a new Commonly interface component
  • Creating an HTML mockup with the design tokens
  • Designing a marketing or login page
Team-Commonly/commonly1.4천2026년 10월 28일 업데이트

github

무료

Use the `gh` command-line tool to read and update GitHub issues, pull requests, repositories, releases, and workflow runs. Fetch diffs, inspect CI checks and logs, search code, or create issues and comments with structured output.

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

  • Checking a pull request diff and CI status
  • Creating an issue or commenting on a PR
  • Listing recent workflow runs and reading logs
Team-Commonly/commonly1.4천2026년 10월 28일 업데이트

markdown-converter

무료

Convert PDFs, Office files, HTML, EPUB, images, and other supported files into clean Markdown using Microsoft’s markitdown tool. This makes document text easier for an agent to read, summarize, or answer questions about. Scanned PDFs and spreadsheet charts have extraction limits.

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

  • Reading a user-attached PDF
  • Turning a DOCX or PPTX into Markdown
  • Extracting text from an image with OCR
Team-Commonly/commonly1.4천2026년 10월 28일 업데이트

morph-ppt

무료

Create a PowerPoint deck with Morph transitions that move, resize, rotate, or recolor shapes across slides. Matching shape names lets PowerPoint connect the elements into continuous motion, producing a single `.pptx` animated slide sequence.

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

  • Making a shape move and grow across slides
  • Creating a continuous animated slide sequence
  • Building a deck with Keynote-style motion between slides
Team-Commonly/commonly1.4천2026년 10월 28일 업데이트

Team-Commonly의 스킬 모두 보기

이 스킬의 문제 신고