Community程式設計與開發github.com

BuilderIO/quick-recap

在每個回應的結尾添加紅/黃/綠狀態區塊,讓完成狀態一目了然,尤其適合已安裝 AGENTS.md 或 CLAUDE.md 管理指令的情境。

quick-recap 是什麼?

這是一個專為 AI 代理人(如 Claude Code、Cursor)設計的輕量級技能,強制在每個工作回應的最末尾加入「紅黃綠」狀態區塊,讓使用者與開發者能快速辨識工作是否已完成、是否還有待辦項目或是否被阻擋。其規則非常明確:綠色代表工作完成且無後續事項;黃色表示有非例行性後續需處理,並簡短說明待辦項目;紅色僅用於需要使用者輸入才能繼續的情況。此外,該技能支援自動化安裝:當專案或使用者的指令檔案(如 AGENTS.md 或 CLAUDE.md)中包含此慣例時,代理人會自動啟用;若手動遵循,則需從使用者角度判斷狀態。支援所有常見的代理人平台,且透過統一的狀態區塊格式,大幅提升回覆的可讀性與溝通效率。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BuilderIO/skills/tree/main/skills/quick-recap

Installed? Explore more 程式設計與開發 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

快速回顧

在每次回應的結尾清楚標示完成狀態。

狀態區塊

每個完成一項工作單元的回應都必須以以下格式結尾:

🟢 實際的簡潔狀態句子

規則:

  • 狀態行保持在 100 個字元以內。
  • 當請求的工作完成時使用 🟢。
  • 當有非例行性後續待辦事項時使用 🟡;指明待辦項目。
  • 僅在被使用者輸入阻擋時使用 🔴。
  • 將狀態行放在回應的最末尾。
  • 不要在狀態行後添加 ---、分隔行或任何內容。

安裝行為

此慣例僅在專案或使用者指令中存在時自動啟用。安裝此技能時,除非使用者選擇退出,否則優先添加受管理的 AGENTS.md / CLAUDE.md 區塊。

如果您手動遵循此慣例,請從使用者的角度選擇狀態:已完成、等待特定非例行步驟、或受阻擋。

範例

工作完成:

🟢 已更新快速回顧文件並附上輸出範例

非例行性後續待辦:

🟡 程式碼已更新,測試 Webhook 前請設定 PROVIDER_WEBHOOK_SECRET

受阻擋,需要使用者輸入:

🔴 需要生產環境 API 金鑰才能繼續

Individual skills in this repo

This repo contains 10 individual skills — each has its own dedicated page.

BuilderIO/adding-a-skill

Use in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill. Covers the repo-local skill files, root catalog docs, plugin metadata, @agent-native/skills dynamic install path, optional managed AGENTS/CLAUDE instruction blocks in ../agent-native/framework, and generated/synced Plan skill gotchas.

BuilderIO/agent-watchdog

Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, inspect what the agent actually changed and verified, report gaps, and optionally make scoped fixes when the user authorizes repair.

BuilderIO/efficient-fable

Use when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy lifting.

BuilderIO/efficient-frontier

Apply the same orchestration as `/efficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.

BuilderIO/plan-arbiter

Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.

BuilderIO/plow-ahead

Use when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done", "finish while I am away", "do not ask questions unless truly blocked", or similar. Convert ordinary ambiguity into stated assumptions, proceed through implementation and validation, stop only for true blockers, and end with a clear recap of decisions, changes, verification, and residual risk.

BuilderIO/read-the-damn-docs

Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces Codex to web-search for current official docs and read primary docs before assuming from memory.

BuilderIO/stay-within-limits

Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.

BuilderIO/visual-plan

Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.

BuilderIO/visual-recap

Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.

相關技能