Skip to content
cccskills
FreePublished on GitHub

working-in-turns

Keep each turn bounded, checkpointed, and reviewable.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly_* MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and work the task board. Load it the moment you see any commonly_* tool available.

The English summary is being prepared. Showing the original description.

Team-Commonly/commonly1.4KUpdated Oct 25, 2026

Use a Commonly pod as shared context for coding work, and post concise handoffs or files to teammates through its MCP tools. Load whenever commonly_* MCP tools are available.

The English summary is being prepared. Showing the original description.

Team-Commonly/commonly1.4KUpdated Oct 25, 2026

Use this skill for ANY visual / UI / design work on Commonly — picking colors, choosing fonts, styling new v2 components, building HTML mocks, designing marketing pages, or auditing whether a change matches the brand. Triggers on tasks involving v2.css tokens, accent / blue / focus ring / SF font, brand mark / logo, design system, design tokens, agent avatars / role tints, pod / chat / inspector / composer styling, marketing landing or login pages, screenshots / demo polish, "make this look better", "design this", "polish UI", "match the brand", "what's the right color/font/spacing/radius". Sources of truth live at `frontend/design-system/` (tokens.css, README.md, brand mark SVG, preview cards) and `frontend/src/v2/v2.css` (production tokens). Read both before recommending or shipping anything.

The English summary is being prepared. Showing the original description.

Team-Commonly/commonly1.4KUpdated Oct 25, 2026

github

Free

Interact with GitHub (issues, PRs, repos, releases) using the `gh` CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.

The English summary is being prepared. Showing the original description.

Team-Commonly/commonly1.4KUpdated Oct 25, 2026

Convert binary documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, images) to clean LLM-friendly Markdown using Microsoft's `markitdown` Python tool. Use when a user attaches a binary file and you need to read its contents.

The English summary is being prepared. Showing the original description.

Team-Commonly/commonly1.4KUpdated Oct 25, 2026

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style transition', 'animated slide sequence', 'shape continuity across slides'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate 1–5a). DO NOT invoke for a generic deck, pitch deck, or board review without cross-slide motion — route those to officecli-pptx base or officecli-pitch-deck.

The English summary is being prepared. Showing the original description.

Team-Commonly/commonly1.4KUpdated Oct 25, 2026

See all skills by Team-Commonly

Report a problem with this skill