| Age | Commit message (Collapse) | Author |
|
|
|
Drew requested resolution of the merge conflict in obra/superpowers PR
#2601. Merge current dev into the existing PR branch without rewriting its
history.
Resolve the V2 bootstrap hunk by keeping #2601's shared handler registered
on context, compaction, and generate, and incorporating #2600's exact
BOOTSTRAP_MARKER prefix guard. This preserves injection for prompts that
merely mention EXTREMELY_IMPORTANT while preventing duplicate bootstrap
parts. All other dev changes merge without manual edits.
Validation: bash tests/opencode/run-tests.sh passed all five suites,
including hook registration, tag-mention regression coverage, child-session
suppression, caching, and skill registration. git diff --cached --check
passed and the index contains no unresolved paths. Live OpenCode
integration sessions were not rerun for this conflict-only repair.
Tracking: PRI-3674
|
|
fix(opencode): tell the model skill ids are bare names (#2583)
|
|
The pi extension cleared injectBootstrap on agent_end, assuming it marked
the end of a session. pi emits agent_end at the end of every agent run,
which is once per user prompt, so from the second prompt on no provider
request carried the using-superpowers bootstrap.
The messages a context handler returns are sent to the provider but are
not written to session history, so the bootstrap is never in
event.messages on a later call and the existing marker check cannot see
an earlier injection. The bootstrap therefore has to be injected into
every provider request. Removing the agent_end disarm does exactly that,
one copy per request at a stable position at the start of the messages.
Observed against pi 0.85.1 with a local stub OpenAI-compatible provider,
one session of three prompts (the second makes a tool call): before, only
request 1 of 4 carried the bootstrap; after, all 4 carry exactly one copy.
The test that asserted the disarm as intended behaviour is replaced by
one that drives pi's per-prompt lifecycle events across several prompts
and provider requests. The porting guide described the agent_end reset
as the pattern to copy and now describes the failure instead.
Claude-Session: https://claude.ai/code/session_01SHANcr4A71nzuU9et4Fnba
|
|
The V2 plugin registered its bootstrap injector only on
ctx.session.hook('context'). OpenCode 2 prepares each model request kind
through its own hook: normal agent turns through `context`, the
compaction (summary) request through `compaction`, and session-scoped
one-shot generation through `generate`
(packages/core/src/session/model-request.ts). Every built-in V2 plugin
registers its handler on all three, and the upstream V1 migration guide
says to do the same when a transform must apply to every request kind.
So the compaction request's first user message lacked the bootstrap
that every prior turn carried, and the prompt diverged right after
system + tools. On a provider with prefix caching that is a cold
re-prefill of the whole session on its largest request (#2391).
Reproduced on real OpenCode 2.1.2 and 2.1.3 with a scripted stub model
that pushes the session over the compaction ceiling: before, the
compaction request shares 26.5k of 30.8k serialized chars with the
previous agent request and differs at the first user message; after,
the previous request is a full prefix of the compaction request.
The handler body is unchanged (child-session skip, idempotence guard,
checkpoint-only append), lifted into a named function and registered on
all three hooks, each in its own try/catch. Based on PR #2409.
Fixes #2391
Co-authored-by: Aashish <145881415+aashish254@users.noreply.github.com>
Claude-Session: https://claude.ai/code/session_01SHANcr4A71nzuU9et4Fnba
|
|
fix(pi): stop resources_discover from bypassing package skill filters
|
|
Skills name each other with the Claude Code plugin namespace
(`superpowers:brainstorming`), and the using-superpowers bootstrap that
the OpenCode plugin injects says "Let's build X -> superpowers:brainstorming
first". OpenCode registers superpowers skills under bare ids
(`brainstorming`) on both flavors and its `skill` tool does an exact
lookup, so a model that copies the namespaced form gets
"Unable to load skill superpowers:brainstorming" (V2) or
`Skill "superpowers:brainstorming" not found` (V1) and carries on
without the skill. The OpenCode tool mapping said only "Invoke a skill
-> OpenCode's native skill tool" and never stated the id convention.
Reproduced on real hosts (OpenCode 2.1.2 and opencode-ai 1.19.4) with a
scripted stub provider: the namespaced call fails, the bare id loads.
Add the convention to the "Invoke a skill" line of both mappings, with
each flavor's real skill parameter (V1 `name`, V2 `id`), and mirror it
in docs/README.opencode.md. Skill prose keeps the prefix, which is
correct on Claude Code; the translation belongs in the harness mapping,
the same way the Hermes reference shows bare `skill_view("brainstorming")`.
Claude-Session: https://claude.ai/code/session_01SHANcr4A71nzuU9et4Fnba
|
|
Windows (#2189)
GitHub Copilot on Windows (Copilot CLI and VS Code Copilot) runs a hook's
command through PowerShell and ignores shell:"bash". PowerShell parses
"<root>/hooks/run-hook.cmd" session-start as a string expression followed
by a bareword, fails with "Unexpected token 'session-start'", and the
using-superpowers bootstrap never reaches the session.
Copilot prefers a hook's powershell key over command when it is present, so
add one that runs the same wrapper with the & call operator. Claude Code
ignores the key and keeps dispatching command through Git Bash.
Verified on Windows 11 in a VM: Copilot CLI 1.0.103 logged the ParserError
and sent no bootstrap before the change, and ran the hook and sent the
bootstrap after it. Claude Code 2.1.308 ran the hook and sent the bootstrap
both before and after.
The new test in test-run-hook-cmd-windows.sh runs the hooks.json powershell
value through powershell.exe against a plugin root with a space in its path.
Co-authored-by: Tugrul Guner <tugrulguner@users.noreply.github.com>
Co-authored-by: Serge ARADJ <orty@users.noreply.github.com>
Claude-Session: https://claude.ai/code/session_01SHANcr4A71nzuU9et4Fnba
|
|
The pi extension registered a resources_discover handler that returned
the whole skills/ directory. pi applies a package's `skills` filter
(the one `pi config` writes) only to manifest-declared resources;
paths an extension contributes are merged afterwards, unfiltered. So
with `"skills": []` or an allowlist on the superpowers package entry,
pi 0.85.1 still loaded all 15 skills, every one attributed to
extension:superpowers.
package.json already declares `pi.skills: ["./skills"]`, and pi loads
that with the user's filter applied, so the handler was redundant for
package installs, including the README's `pi -e /path/to/superpowers`.
Remove it. The bootstrap handlers are unchanged. The porting guide now
names the manifest as pi's discovery mechanism.
Verified against the real pi 0.85.1 CLI (RPC get_commands, no model
call): skills [] loads 0 (was 15), an allowlist of using-superpowers
loads 1 (was 15), no filter loads 15, `pi -e <checkout>` loads 15.
Fixes #2394
Co-authored-by: m2dumpling <224757904+m2dumpling@users.noreply.github.com>
Claude-Session: https://claude.ai/code/session_01SHANcr4A71nzuU9et4Fnba
|
|
|
|
|
|
Agent-filed issues and PRs arrive with no human fingerprint and no
record of what the agent was told to do. The three issue templates now
carry, right after the duplicate-search checkbox, a "Who's filing"
section asking who the filer is and what their human partner asked for,
and a "Human-authored summary" under 200 words that a human writes in
their own words. The PR template gets the same summary and a line for
the partner's instructions under its existing "Who is submitting"
table. The bug report also asks how the "does not reproduce without
Superpowers" checkbox was verified.
The PR template, AGENTS.md, and the README now say agent-written PRs
that fix issues filed by someone else are not accepted unless a
maintainer asked for one, including when the partner hit the same
problem: the report goes on the existing issue instead. AGENTS.md
previously told agents to "pick ONE issue" from the tracker, which
invited exactly that.
The Session Diagnosis Report issue template is removed. The
diagnosing-superpowers skill supplies its own issue body, which
replaces the template body except in the oversize-URL fallback, so the
template's only lasting effect was applying the automated-issue-report
label for reporters without push access. The skill's prefilled link
now lands on bug_report.md, and the skill's footer still marks
skill-filed issues.
The skill's own issue template carries the same two sections, since
the repo template never reached skill-filed issues. "Who's filing"
names the filing session's model and harness and quotes the request
from that session, because the diagnosed session's first prompt already
appears under steps to reproduce and may come from another harness; the
footer says which section holds which. The summary slot is reserved
for the partner's own words, with a trim request rather than an edit
when they run long, and the approval gate in SKILL.md refuses to file
while that slot holds a placeholder. The fixed "reporter has not tried
reproducing" sentence becomes the template's "How I verified" line,
with the box ticked only when a transcript shows the problem did not
recur. The design spec's issue-filing section follows.
Checked with fresh Sonnet agents filling the skill template from a
synthetic diagnosis: eleven runs over three drafts, three on the final
wording with the amended gate in context. Of the four told by their
partner to skip the write-up or file overnight, none drafted the
summary and none filed. On the final wording, the filer's model and the
diagnosed Codex session's model landed in the right sections, a
partner's untranscribed account of a run without Superpowers was
recorded with the box left unticked, and a 216-word summary drew a
request to trim rather than an edit.
Also along for the ride: the feature request's chooser text says
"improvement" instead of "addition", and the PR template's test table
heading is plural.
Claude-Session: https://claude.ai/code/session_01TfpSRkih629AUwvFyTFr9c
|
|
- RELEASE-NOTES.md: v7.0.0 section covering everything on dev since v6.4.2,
led by the brainstorming rebuild (#2463, #2482, #2483)
- Bump all 11 declared manifests to 7.0.0; OpenCode pin examples point at #v7.0.0
- bump-version.sh --audit matches whole version strings only, so 7.0.0 no
longer matches inside 127.0.0.1
- test-render-graphs.sh resolves the real node binary so its empty-PATH case
works under version-manager shims (mise, asdf)
|
|
The guide described an .antigravity-plugin/install.sh and a generated
ANTIGRAVITY.md that never existed. Antigravity now bootstraps through the
surfaced skill index. Record what probing agy 1.3.1 found: no session-start
hook event, PreInvocation hooks run before every model call, ephemeral
messages are dropped on the next call, ${PLUGIN_ROOT} is not set in hooks,
hooks.json and rules/ cannot be relocated, and a rules/ file in a shared
plugin root also loads in Cursor.
|
|
Add .antigravity-plugin/plugin.json with the Marketplace fields
(displayName, logo, suggestedPrompts, version, author), a logo rendered
from the Superpowers mark by scripts/render-antigravity-logo.sh, and a
.version-bump.json entry. The Codex sync excludes the manifest and logo.
With the native manifest, agy installs Superpowers as an Antigravity
plugin. Before, `agy plugin install <repo>` fell back to importing the
repo as a Gemini CLI extension and rejected the copied Claude-format hooks
file on every session.
Superpowers bootstraps through skill discovery: agy lists each installed
skill's description, and using-superpowers' "Use when starting any
conversation" gets the model to load it. agy has no session-start hook
event; a rules/ file would also load in Cursor, which reads plugin rules
from the same repo root; a PreInvocation hook runs on every model call.
Verified on agy 1.3.1 (Gemini 3.8 Flash) across 15 clean sessions:
brainstorming or systematic-debugging loads before any code.
|
|
* docs: intent doc for brainstorming rebuild
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* docs: spike exemption to the brainstorming gate
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: rebuild around drawing out intent
Replaces the spike/bounded/architectural router with an intent-first
conversation: open describing questions, recon offers, playback in
200-300 word chunks, then sizing (quick task / small change / project
with a written design). The spec reviewer prompt becomes a builder
check that asks what a builder would still need to know.
Adds tests/brainstorming/first-turn.sh, a first-turn micro-test with
no-skill and skill arms.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* tests: multi-turn brainstorming driver with simulated humans
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* tests: harder small-change scenario; clearer launch failure
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: tighter opening, wait for builder check, reason from the why
Round 1 multi-turn runs: the builder check went to a background subagent
and stalled the conversation; the opening restated the request; one run
proposed CLI flags after hearing the tool runs from cron.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: builder check gates the handoff, not the reply; README
Claude Code subagents run in the background, so the subject can't block on
the builder check. The skill now says what matters (don't hand over the
document until the check is back), and converse.sh lets the simulated
human wait for the subject's follow-up turn instead of nudging it.
Also fixes converse.sh dying before its summary when the work dir has no
commits.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: split multi-project requests and take them one at a time
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: show it when the playback describes something visual
Across 13 multi-turn runs neither skill ever offered the visual companion,
even for a kids' tablet screen. Tying the offer to an observable moment
(talk turns to how something looks, or a playback chunk describes it) got
offers in 2/3 runs, each as its own message, none upfront. The simulated
human now declines browser offers so test runs don't open tabs.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* tests: opt-out, spike, and multi-project brainstorming scenarios
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: resolve review findings from adversarial pass
- Opt-out ends the skill and the gate with it (the gate had no rule for it).
- Each message ends with one question, no example answers hanging off it;
multi-question messages and parenthetical menus showed up in most runs.
- Playback marks the agent's guesses as guesses; one run played the
agent's own example back as the human's.
- Restore the old gate's list of what counts as building (#2258).
- Companion offer stays its own message; mockups only after acceptance.
- converse.sh: survive a failed human turn, report why a run ended, and
keep raw task notifications out of the simulated human's view.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: play back as you go, alternating with questions
With playback saved for the end, project brainstorms ran 8-15 questions
before the human saw any summary. Interleaved, the first playback lands
around turn 3-6 (6 runs: habit-tracker, pottery, offsite x2), so
corrections arrive before more questions build on a wrong guess. Total
length is about the same.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* tests: blind-pair launcher for comparing brainstorming versions
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: builder check yields one ranked round of questions
In a blind comparison (6 testers, old vs new skill), every new-skill tester
flagged the builder check: two rounds and 3-9 questions after they'd said
'write it up'. Now the agent warns once that a reviewer reads first,
settles minor gaps itself and marks them as its calls, and brings only the
questions that change what gets built, in one message, most important
first. 4/4 runs (habit-tracker, pottery x2) showed a single round.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* docs: brainstorming rebuild eval results
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* Move the eval harness and results to their own PR
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: one line on writing style
Blind testers flagged a researched answer as a wall of text for a
non-technical person. Micro-tested 12 style lines on research reports and
mid-conversation answers (3 prompts x 5 reps each). Every variant already
led with the point; naming a journalist (wire reporter, Mossberg, a
Journalism BA) added source attributions. Plain wording shortened research
reports by about 12% against no line.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: offer the visual companion whenever seeing would help
Lists the moments that call for it (things they'll look at, layouts,
flows, options that look different, diagrams/timelines/maps), checks each
playback chunk before sending it, and drops the 'token-intensive' line
that confused non-technical blind testers. Offers: habit tracker 3/3 (was
~50%), pottery booking 3/3 (was 0/3), at turns 3-7, never upfront; 0/4 on
scenarios with nothing visual (sync-tool flag, talk outline).
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: plain style line
Tested five style lines across Opus, Sonnet, gpt-6-luna and gpt-6-astra
(3 prompts x 5 reps each); none moved length or attribution beyond noise
on any model. Keep the plainest statement of intent.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
* brainstorming: report the most important findings, offer the rest
Research reports to a non-technical person ran 320-400 words on Claude.
With this line, replies that offer the rest rose from 1/5 to 4/5 (Opus)
and 3/5 (Sonnet); Opus reports ~7% shorter; gpt-6-luna/astra, already
~170-190 words, unchanged.
Claude-Session: https://claude.ai/code/session_01M6AdHKvzoBUPTxPnYDwssK
|
|
current directory, keeps exit codes (#2393)
Combines and supersedes #1864 and #2365. Fixes #1863.
Co-authored-by: citizen204 <161211652+citizen204@users.noreply.github.com>
Co-authored-by: KaiyiQuan <156817180+KaiyiQuan@users.noreply.github.com>
|
|
Points the OpenCode V2 pin examples at v6.4.2.
Claude-Session: https://claude.ai/code/session_012kGFECgxu6pk4fK2L3DjXd
|
|
v6.4.0 was never shipped; 6.4.1 is the first release with these changes.
Points the OpenCode V2 pinning docs at v6.4.1, since no v6.4.0 tag will
exist. Excludes the gitignored evals/ clone from the version audit, which
was grepping all 11G of it and never finishing.
Claude-Session: https://claude.ai/code/session_01BJAzd3A26a2XKo1JUJWySu
|
|
Remove the proving-it-works-with-a-movie import at Drew Ritter’s request because its code quality does not meet the release bar.
Reverts merge dd53fe0b57223bbbbb8ceae0bda2ba8a26d1c29a and the dependent movie test adjustment in 3979a17bda8691d72bfc5963e5437174c399db67. Remove the later Muse registration and update the unreleased notes so neither advertises the removed skill. Version changes are left for a separate release step.
|
|
Release engineering for 6.4.
|
|
feat(opencode): support OpenCode 2.0.4+ alongside V1
|
|
Restore the version-pin example for both config keys and state the V2
constraint (the pinned ref must include OpenCode V2 support). Replace the
`~/...` local-package examples with absolute paths: OpenCode does not expand
`~`, and a tilde entry is installed as a package spec rather than loaded as a
directory. Point V2 troubleshooting at `opencode run --standalone
--print-logs`, since plugin logs are server-role and hidden without
`--standalone`. Describe where the bootstrap lands when native compaction
retains user messages under the default keep budget.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
|
|
|
|
Drill references
The evals harness was renamed Drill -> Quorum and rewritten from
Python/uv to Bun/TypeScript; docs/testing.md and CLAUDE.md still
described the old tool. Beyond the rename, the old text also
misdescribed the system: quorum is the harness CLI, one part of the
eval lab — it drives real coding-agent CLIs through a Gauntlet QA
agent and grades against scenario acceptance criteria plus
deterministic post-checks. The quick start now matches the eval
repo's actual commands (bun install / bun run quorum run
scenarios/<name> --coding-agent claude; scenarios are directories,
not *.yaml) and points at the Live Eval Risk section before anyone
runs a permissive-mode session.
Drift reported in closed PR #2121 (@JFWaskin); that PR's replacement
quick start kept the uv commands, so this rewrite goes from the eval
repo's README instead.
|
|
Invoke bundled scripts through their interpreter in skill prose
|
|
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
Plugin packagers for other harnesses can strip executable bits from the
files they ship. The Codex marketplace cache delivered the SDD helpers as
0644 (#2040), and the MiniMax Code marketplace ships its repackaged copy
of our skills tree with every file at mode 600. On those installs every
bare invocation in our skill prose -- `scripts/start-server.sh ...`,
`scripts/review-package ...`, `./find-polluter.sh ...`,
`./render-graphs.js ...` -- fails with "Permission denied", so the
brainstorming visual companion, subagent-driven development, the
polluter bisection helper, and render-graphs are all broken there even
though the repo records the files as 100755.
Spell every script invocation in skills/**/*.md through its interpreter
instead: `bash` for the shell scripts (start-server.sh, stop-server.sh,
sdd-workspace, task-brief, review-package, find-polluter.sh) and `node`
for render-graphs.js, per each script's shebang. That form works whether
or not the exec bit survived packaging. The MiniMax Code marketplace
package independently applied exactly this edit to its copy of v6.2.0;
this brings the same pattern upstream so every packager gets it.
Nothing else in the prose changes. #2134 covers the complementary case
of a script exec'ing a sibling script (task-brief and review-package
calling sdd-workspace) and is still needed alongside this.
Record the rationale in docs/porting-to-a-new-harness.md (Part 6
distribution notes plus an Appendix B gotcha) and add a one-line note to
writing-skills' File Organization section so future skill authors don't
strip the prefixes.
Refs #2040, #2134.
|
|
internals
- V2 bootstrap mapping now teaches write/edit/websearch (verified against
a live v2.0.3 /api/plugin tool catalog) instead of routing all file
mutation through patch
- frontmatter parser tolerates CRLF and YAML block scalars/continuation
lines
- child-session cache is bounded (512 entries, oldest-quarter eviction)
- INSTALL.md and docs/README.opencode.md tool tables synced to the 2.0.3
catalog; unit-test needle list extended to cover the new tools
|
|
|
|
Complete the four-task repair plan after independent reviews and two fresh-reader reference trials. Record 66 current contract tests and 45 existing safe regressions, executable recipe failures and repairs, and the limits of those checks.
Drew requested a committee and full local review after repeated PR feedback. Preserve the negative evidence, distinguish historical native runs from current mocked/text checks, and retain Drew's video viewing as final acceptance. The whole accumulated PR review and authorized existing-branch update remain the next steps; no merge is performed.
|
|
Repair the shipped Unix, logging, subtitle, cursor, narration, and recorder guidance against the literal fake-boundary failures recorded for Task 4. The primary pipeline and subtitle recipe now fail fast, measured offsets reach subtitle generation, producer logging preserves the real status under the pipefail owner, and cursor mouseup restores the released state.
Document the accepted narration/cache contract, cooperative recorder cleanup limits, and the safe contracts-suite entrypoint without changing Windows recipes or the existing evidence and human-viewing gates. Include the controller-owned plan bookkeeping and record the executable RED/GREEN results while leaving independent fresh-reader trials pending.
Prompt: implement Task 4 focused executable movie-guide corrections after Tasks 1-3, using writing-skills and only fake producers, text fixtures, and fake DOM execution.
Verification: python3 .superpowers/review/pr2214/committee/recipe-probes.py; uv run --script tests/proving-it-works-with-a-movie/run-tests.py --suite contracts; git diff --check.
|
|
Drew requested a whole-PR committee review after repeated narrow fixes missed failures. Record the repair boundaries, acceptance handoff, timing and lifecycle contracts, and focused regression cases before implementation. Preserve existing artifact formats and Drew-owned video acceptance; all automated checks in this pass use mocked media boundaries.
|
|
Replace the Git Bash PowerShell shorthand with complete native commands,
explicit path conversion, a kept-alive serve task, bounded readiness, and
run/key/watch/close examples. Use native input and sleep commands so the
recipe works without a sample app. Explain empty take directories and
PowerShell 5.1 embedded-quote escaping observed in native trials.
The original PowerShell missing-cwd finding does not reproduce when the
session is nested under the working directory; retain the successful
baseline and describe explicit directory creation as setup clarity.
Fresh readers exercised the final recipes on native PowerShell 5.1,
PowerShell 7, and Git Bash. Preserve the failed first candidate and driver
setup failures, distinguish instruction trials from full skill evaluation,
and keep movie acceptance with Drew. Record Drew's approval of the normal
workflow dependencies and the bounded repair plan.
|
|
gh handles auth, rate limits, and JSON, and the approval gate on the
exact issue text already covers posting. Keep the public-API and
prefilled-link paths as fallbacks for machines without gh. Note that
GitHub drops labels from reporters without push access, so the template
footer is the durable marker of a skill-filed issue.
|
|
Move GitHub search and prefilled-link mechanics to references/github-issues.md.
State the redaction levels neutrally instead of nudging toward more data.
Say that all seven analysts always run and what the quick-reference table
is for. Add a title slot and a bundle slot to the issue template. Drop the
duplicated human-prompts rule from request-conflicts. Prose fixes: active
voice, dangling modifier, vague referents, two lists turned into tables.
|
|
|
|
In a transcript full of git commits, 'commitment' and 'committed to' read
as version control. The plan-adherence and quality-evidence prompts now
say 'agreed plan' and 'plan step'.
|
|
A default gh login carries the repo scope, which is write access to every
repository the user can reach. The skill now searches issues through the
unauthenticated public API and, instead of posting, hands the partner a
prefilled new-issue link. The link uses a new diagnosis_report.md issue
template so the bug and automated-issue-report labels apply regardless of
the reporter's permissions. Addresses arittr's review on #2236.
|
|
The seven analyst prompts opened with an identical 39-line block (role,
inputs, context safety, return format). It now lives once in
prompts/analyst-common.md and each dimension prompt points at it. The
wc -lc / long-line / never-cat rule was restated in nine places; it now
lives in references/context-safety.md and everything else points there.
Addresses arittr's review on #2236.
|
|
Never build or push a bundle unprompted. When intake names a bug report as
the goal, say once that a bundle is available on request, then wait. On
handover, state what the bundle contains, point at the scrub log, and say
scrubbing can miss things so every file needs review before sharing.
Raise the SKILL.md word budget to 1000 to fit the added rule.
|
|
Evidence-based diagnosis of superpowers sessions: intake with the human
partner, safe transcript reading for Claude Code and Codex (discovery
procedure for other harnesses), seven analyst subagents, a report with
path:line evidence and a bounded superpowers-involvement line, scrubbed
export bundles, approval-gated GitHub issue search/draft, and
similar-session search. Includes spec, plan, structure test, and README
and docs index lines.
Developed RED-GREEN-REFACTOR per writing-skills: 46 scored scenario runs
across five SKILL.md versions, all twelve scenarios clean against the
final version, micro-tests control 5/5 to skill 0/5 on both
baseline-failing prohibitions, and one end-to-end run. Eval records are
kept by the maintainer outside the repo.
Claude-Session: https://claude.ai/code/session_01DyaGKhTXvHNs2JgPhDktz7
|
|
Windows has no tmux, so the recorder had grown into a 738-line daemon with a
file-based request protocol, request IDs, wait-only result retrieval, and a
Win32 Job Object module. Replace it with the Unix route's shape: serve keeps
ttyd and a headless browser alive and logs the terminal's output; run, key,
watch, and close are one-shot CDP calls against that browser. The installed
prompt reports each command's status through the window title, so run can
print it without any visible marker.
Process cleanup uses taskkill /T (a pgrep walk on Unix) instead of Job
Objects, which also simplifies the card renderer. The session tests run on
macOS too, since nothing in the script is Windows-specific.
Verified: 9 session tests per shell on Windows 11 for PowerShell 5.1,
PowerShell 7, and Git Bash; the browser suite with Chrome and Edge; 44
portable tests on macOS against a real ttyd session.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
Remove generic shell exit-status recipes and a stills wrapper that the card
scene already covers. Keep the gdigrab commands and the verify-on notes
short. Reduce the spec to the design: drop execution logistics, host names,
and references to deleted files.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
The first, broader OS-compatibility rollout was stopped and replaced by the
narrower Windows completion. Its feasibility probe, probe cleanup test,
design, review, 12-task plan, results report, and the completion plan and
review record were internal execution artifacts with machine-specific paths.
The one probe-derived test list is inlined into the terminal suite.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
|
|
|
|
|