Skip to content

feat(skills): open-threads — sweep recent sessions, propose a consolidated spawn plan - #648

Draft
aarontrowbridge wants to merge 1 commit into
mainfrom
646-open-threads-skill
Draft

feat(skills): open-threads — sweep recent sessions, propose a consolidated spawn plan#648
aarontrowbridge wants to merge 1 commit into
mainfrom
646-open-threads-skill

Conversation

@aarontrowbridge

Copy link
Copy Markdown
Member

Closes #646

What

A public skill that turns the fleet's chat history into a resumption plan: sweep recent sessions, classify open threads, consolidate the spawnable ones into a few theme-scoped fresh sessions, and — on confirmation — spool them via amicode_session (#641).

The doctrine, in one line: one session per THEME, never one per thread; BLOCKED-ON-USER and AWAITING-REVIEW threads are reported, never spawned; seed prompts are self-contained (paths, PR numbers, parked next-steps verbatim) because the child session starts with zero memory of the sweep.

Contents

  • packages/extension/skills/open-threads/SKILL.md — frontmatter per convention (surface: public, agents [researcher, director]), usage block, and the full procedure: DB resolution (OPENCODE_DB → default path, read-only URI, run-on-the-server rule), the tested SQLite recipe, classification buckets, consolidation rules (cap 3–4, tab-label titles, fresh vs the rare fork), the question-tool confirm gate, and the honest degradation path when the spawn tool isn't deployed.

Evidence

  • The skill's Step-1 recipe was extracted verbatim and run against the live fleet-server DB: 97 sessions in a 14-day window → 60 after the noise filter; pending-todos and last-assistant-text extraction both working.
  • Frontmatter parses (name/surface/agents validated).
  • The sweep this skill codifies was exercised live earlier today at the user's request (the "open threads from recent sessions" pass) — the procedure is the prototype, the skill makes it repeatable.

Sequencing

Depends on nothing at runtime — the skill degrades honestly when amicode_session (#641) isn't deployed yet (report + inline-continuation offer). Once #641 lands and ships, the spawn step activates.

…dated spawn plan (#646)

The fleet's aggregated chat DB holds weeks of unclosed threads; nothing
surfaces them. This skill codifies the sweep-and-resume pass: a read-only
SQLite recipe (top-level sessions in a window, last assistant text per
session, pending todos), a five-bucket classification (BLOCKED-ON-USER /
INTERRUPTED / PARKED / AWAITING-REVIEW / STALE), consolidation of spawnable
threads into at most 3-4 THEME-scoped sessions with self-contained seed
prompts, and — only on explicit confirmation — one amicode_session call per
theme (#641's spawn tool; graceful inline fallback when it isn't deployed).

The DB recipe is verified verbatim against the live fleet server DB
(97 sessions in a 14-day window → 60 after the noise filter; todo and
last-text extraction working).

Blocked-on-user and awaiting-review threads are deliberately never spawn
candidates — a fresh session cannot press the button only the human can
press.
@coderabbitai

coderabbitai Bot commented Aug 30, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

skill: open-threads — sweep recent sessions, propose a consolidated spawn plan

1 participant