Skip to content

t1k:cocos:playable:stdlib-scan

FieldValue
Moduleplayable
Version4.33.13
Effortlow
Tools—

Keywords: candidate queue, dry-run detector, pending stdlib candidates, quét code tái sử dụng, reusable code candidates, stdlib candidates, stdlib scan, what would the detector flag

/t1k:cocos:playable:stdlib-scan
[<project-root>] [--files a,b] [--list-rejected] [--queue]

The model-invocable, read-only front door to the stdlib candidate detector. It answers “is there reusable code in this project, and is the queue waiting on anyone?” without starting a harvest run. t1k-cocos-playable-stdlib-harvest stays disable-model-invocation: true; this skill is the part of that pipeline that is safe to start on a model’s own judgment.

StageCommandWrites
Dry-runbun <HS>/scripts/stdlib-candidates.cjs dry-run --project <root> [--files a,b] [--list-rejected]nothing
Statusbun <HS>/scripts/stdlib-candidates.cjs status --project <root>nothing
Reportbun <HS>/scripts/stdlib-candidates.cjs report --project <root>nothing
Queue (only with --queue, after the dry-run)bun <HS>/scripts/stdlib-candidates.cjs scan --project <root> --files <the flagged files>the per-user local candidate queue under $HOME/.claude/session-state/stdlib-candidates/

<HS> is .claude/skills/t1k-cocos-playable-stdlib-harvest (the detector ships with that skill).

Nothing here writes to a shared repo, opens a PR, posts to Discord or spawns a contributor. The only write is the queue file, which lives in the user’s home, not in the project and not in any repository. Those steps belong to the harvest skill and t1k-cocos-base-stdlib-contribute, run by a person (or by the nudge’s mode=auto flow, which stops at a draft PR).

  1. Resolve the Cocos project root (package.json carries creator.version). Not a Cocos project: stop and say so.
  2. Run the dry-run. Read flagged, wouldQueue, wouldDropAtCeiling and rejectedByReason. Zero flagged with a large rejectedByReason count means the thresholds, not an idle project.
  3. Only when the user asked for --queue (or the dry-run shows wouldQueue > 0 and the user confirms): run scan over the flagged files. droppedAtCeiling in its output is not silence, report it.
  4. Report: flagged count, the top symbols by file, the queue summary, and the next step. The next step is brief plus triage by the nudge’s flow, never a PR from this skill.
  • Do not run harvest, brief, ingest, ack or purge from here: they change triage state.
  • Do not treat vendored foundation folders (for example *GameFoundation/) flagged by the dry-run as project code to contribute: they are template glue and the reuse loop reports them, it does not copy them.