Repository navigation
Fix the interrogate spawn wording - #32
Conversation
Code-format spawn_subagent, say each reviewer omits subagent_type, and restore the separate PR to update the default table. Co-authored-by: Kaitian Xie <caelaxie@users.noreply.github.com>
caelaxie
left a comment
There was a problem hiding this comment.
pass. matches #28's smallest fix exactly: spawn_subagent code-formatted, "omits subagent_type", and the upstream "open a separate PR to update the default table" clause restored; grok path/model substitutions kept. one file, 3/3 lines, no cursor paths. Validate plugin (validate + install --trust + list + inspect) green at 1cd826d, accepted as proof for a text-only fix. closes #28 linked, not a draft. squash-merging.
|
Harness at head Installed checkout
Rest of CI, on this head: frontmatter check A live Installed Launch all reviewers in a single message with `spawn_subagent`, one per entry on the `interrogate reviewers` line in `~/.grok/rules/pstack-models.md`, labeled Reviewer A, B, and so on to match the entry count. If the rule or that line is missing, use the table defaults.
Each reviewer omits `subagent_type`, a prompt that forbids file edits (there is no readonly flag), and `model` set to its configured entry, or its table default when there is no configured line. Omit `model` for an `auto` or `inherit-parent` entry, so that reviewer runs on the parent model.
If `spawn_subagent` has no `model` argument, omit it for this session so the child inherits the parent, and apply step 1 of **setup-pstack** so the next session can pass `model`. If it rejects a configured entry, use the closest slug from `grok models` and say so, and open a separate PR to update the default table. Prefer a detected slug different from the parent's when one exists. Do not block the review on the slug issue. Never treat an alias entry as a rejected slug. |
In
skills/interrogate/SKILL.md:spawn_subagentis code-formatted.subagent_type.Closes #28