setup-benny
Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- setup-benny
- description
- Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.
- disable-model-invocation
- true
03 SKILL.md 正文
Set up Benny
Benny ships as a dormant automation pack inside pstack. The pi-pstack package exposes only its normal skill root; this file and the two operational files are not slash skills.
The human enters setup by pointing Pi at the pack's FOR_AGENTS.md. The bootstrap flow copies the whole pack into the target repository, then reads this file directly at .pi/automations/benny/skills/setup-benny/SKILL.md.
Benny needs external configuration and two live pi-pstack automations.
Do not create or update an automation until the user explicitly asks. Never put a secret value in package files, prompts, or committed configuration.
1. Copy the pack and enable shared pstack skills
Do this before asking for Benny configuration and before invoking the automate skill pi-pstack ships (/automate).
Ask which repository will run the automations. The source pack is the directory containing FOR_AGENTS.md. The destination is <target-repository>/.pi/automations/benny/.
Merge the entire source pack into the destination:
- Create the destination when it is absent.
- Copy every source file to the same relative path.
- Preserve destination-only files. Never delete unrelated files during install or refresh.
- Keep user-owned configuration, feature maps, and routing maps outside the destination. Never overwrite them.
- When an existing source-managed file differs, inspect the diff and merge without discarding local edits. If ownership is ambiguous, stop and ask before replacing it.
- Verify that the destination contains
FOR_AGENTS.md, this setup file, both operational files, their references, and the templates.
If this file is already being read from the target destination, treat the copy as complete and run the same verification before continuing.
Add pi-pstack to the target repository's .pi/settings.json (what pi install -l npm:@justjoshn/pi-pstack writes). If the file or .pi directory does not exist, create it.
Merge this entry into the existing JSON or JSONC:
{
"packages": ["npm:@justjoshn/pi-pstack"]
}
Preserve every unrelated top-level setting and every other package entry. If packages already lists pi-pstack (by npm name, git URL, or path), leave that entry as it is. Preserve comments and valid JSONC syntax when the file uses JSONC. Validate the file after editing it.
Reload the target project or start a fresh agent rooted there. Verify that these shared pstack skills resolve from project scope:
howwhytddunslopprinciple-separate-before-serializing-shared-stateprinciple-minimize-reader-loadprinciple-guard-the-context-windowprinciple-sequence-verifiable-unitsprinciple-fix-root-causesprinciple-prove-it-works
Do not count a skill loaded from the current session or a user-scoped install. The check must show that a fresh agent in the target repository receives pstack through project settings.
If project-scoped package installation is unavailable or any shared dependency does not resolve, stop and explain the failure.
The Benny files are read directly from .pi/automations/benny/. Do not add that directory to a skill path or a manifest or expect its SKILL.md files to appear in the slash-skill list.
Tell the user that .pi/settings.json, .pi/automations/benny/, and any referenced secret-free configuration must be committed before either automation is enabled. Do not commit them unless the user asks.
Once this check passes, live automation prompts may read the committed operational files by their stable repository-relative paths. They must not embed a pi-pstack package path or copy the file contents.
2. Adapt the configuration
Open these copied examples:
../../templates/configuration.example.yaml../reproduce-and-fix-issues/references/feature-map.example.md
Create user-owned copies outside .pi/automations/benny/. These are configuration files, not pack files. Example locations:
- Project config, such as
.pi/benny/configuration.yaml - Project feature map, such as
.pi/benny/feature-map.md - Project routing map, such as
.pi/benny/routing.md - User config, such as
~/.config/benny/configuration.yaml - User feature map, such as
~/.config/benny/feature-map.md
Fill one feature-map section for every user-facing feature the automation may reproduce. Keep it at the user point of view. Do not freeze implementation details or current code paths in the map.
Do not edit the copied examples. Pack refreshes may update source-managed files after conflict review, but they must never touch the user-owned copies.
Prefer committed, secret-free files in the target repository when a fresh automation checkout must read them. Otherwise paraphrase the required values into the live prompt. Reference a repository file only after the automate skill confirms that the file is committed in the repository where the automation runs.
Use stable repository-relative paths for committed pack and configuration files. Never reference the pi-pstack package directory from a live automation.
3. Fill the required choices
Ask for or confirm:
- Source Slack channel ID
- Optional operations or status channel ID
- Repository URL and default branch
- Triage identity or Slack user ID
- Issue tracker type, team, project, labels, and intake status
- Tracker adapter skill or MCP actions
- Optional routing map path
- Required control skill name
- Required user-facing feature-map path
- Status emoji strings
- Pull request URL format
- Polling and effort budgets
- Model slug for triage, repro, code work, and media review
Use only models listed as available in <pstack_subagents> or pi --list-models. Do not guess a slug and do not carry over a private default.
The source channel, triage identity, repository, tracker adapter, control skill, and feature map must be explicit. Fail setup if any required value stays ambiguous.
Use pstack's unslop skill on the final automation names, descriptions, and prompt shims before saving them.
4. Check integration capabilities
The triage automation needs:
- Read access to the configured source Slack channel and its threads
- Thread-reply access in that channel
- Attachment metadata and file download access when reports include media
- Search, read, create, and update access through the configured issue-tracker adapter
The repro automation needs:
- Read access to the source thread
- Thread-reply access in the source channel
- Optional post and edit access in the configured operations channel
- Repository read and history access
- A pull request action that can open a draft pull request
- The configured control-adapter skill
Prefer pi-pstack's Slack tools (slack_read_thread, slack_send, slack_react, slack_update) for reads and posts; they work once the Slack bot token is stored with request_secret (connector slack, field token). The optional BENNY_SLACK_BOT_TOKEN may fill a narrow gap such as editing one operations status message or downloading an attachment. Store the value in a secret manager or environment, not in YAML.
Do not use undocumented integration endpoints.
5. Prepare the routing map
If the user wants reroutes or owner pings:
- Copy
../triage-issue-reports/references/routing.example.mdoutside.pi/automations/benny/. - Replace every placeholder with public or organization-local values.
- Keep owner pings off by default.
- Allow a ping only for a configured feature owner or a confirmed likely regression author.
If no routing map is configured, triage may classify a report but must not guess a destination or owner.
6. Verify the control adapter
Read ../reproduce-and-fix-issues/references/control-adapter.md and the user's completed feature map.
Confirm that the named skill can:
- Bring up the target app
- Navigate every mapped feature through the real UI
- Exercise mapped states through declared adapter actions
- Inspect state without forcing the result
- Capture screenshots
- Start and stop a recording
- Clean up its processes and temporary data
If any capability is missing, leave the repro automation disabled. It must fail closed rather than claim a reproduction it did not perform.
7. Prepare the live automations
Ask whether this is first-time creation or configuration of existing automations.
Read ../../FOR_AGENTS.md from the copied pack as the primary user-intent source for either path. Use it to understand the two triggers, tools, instructions, outcomes, and shared rules.
First-time creation
Create one automation at a time.
For each automation:
- Read the matching copied prompt template as secondary internal source material.
- Turn
FOR_AGENTS.md, the finished Benny configuration, and the template intent into a complete natural-language request. - Tell the live prompt to read and follow its exact committed operational file under
.pi/automations/benny/. - Use the stable repository-relative path, not a pi-pstack package path. Do not copy the operational file contents into the live prompt.
- Read and follow the
automateskill pi-pstack ships (/automate). Create each automation withsessionStrategy: "new_session"andenvironment: "cloud", so every run starts on its own cloud machine with a fresh clone of the configured repository and branch. - Let
automatediscover the Slack channel (withslack_read_channel), the repository, and connected integrations. - Let
automateconfirm that the copied pack and any referenced configuration files are committed in the same repository where the automation will run. - Let
automateshow its draft table, obtain approval, ask readiness, create the automation, and hand it to/automations. - Finish the
/automationshandoff for this automation before starting the next one.
Give automate this complete triage intent, filled from configuration:
- Name
benny-triage. - Read and follow
.pi/automations/benny/skills/triage-issue-reports/SKILL.mdfor every run. - Trigger on each new top-level report in the configured source Slack channel.
- Read the triggering thread and reply only inside it.
- Use the configured issue-tracker integration.
- Classify, inspect evidence, trace cause, dedupe, and create only clear new bugs.
- End one thread-only verdict with the configured
[benny:bug],[benny:performance], or[benny:other]marker and optional tracker URL. - Never post a source-channel root message.
After the triage /automations handoff is complete, give automate this complete repro and fix intent:
- Name
benny-reproduce. - Read and follow
.pi/automations/benny/skills/reproduce-and-fix-issues/SKILL.mdfor every run. - Trigger on the same new top-level reports in the configured source Slack channel.
- Use the configured repository and default branch.
- Read the source thread and reply only inside it.
- Include pull request creation and the configured tracker, control-adapter, and feature-map requirements. Paraphrase mapped user paths and states unless
automateconfirms an eligible committed file in the same repository. - Wait for a trusted triage marker before acting.
- Reproduce the exact symptom twice through the mapped real UI and capture evidence.
- Verify an existing fix without authoring over it.
- Attempt an optional bounded fix only after confirmed repro, then open a draft pull request when proof and checks pass.
- Never post a source-channel root message.
Do not duplicate automate's Slack, repository, integration, completeness, authentication, draft-review, approval, readiness, or editor-handoff work.
Existing automations
The automate skill is creation-only. Do not use it to search for, inspect, or update existing automations.
Finish configuration, routing, control-adapter, and feature-map validation. Then give the user this concise editor checklist.
For the existing triage automation, update:
- Name and description
- Direct instruction to read
.pi/automations/benny/skills/triage-issue-reports/SKILL.md - New top-level Slack report trigger and source channel
- Slack thread read and reply capabilities
- Issue-tracker integration
- Paraphrased triage instructions, thread-only rule, and Benny verdict markers
For the existing repro automation, update:
- Name and description
- Direct instruction to read
.pi/automations/benny/skills/reproduce-and-fix-issues/SKILL.md - Matching Slack trigger and source channel
- Repository and default branch
- Slack thread read and reply capabilities
- Pull request action
- Tracker, control-adapter, and feature-map requirements
- Paraphrased marker wait, evidence, verification, and bounded-fix instructions
Ask the user to update each existing automation with /automations edit <name>. Do not create replacements or duplicates.
Creation boundary
Never write the subscription registry, a supervisor file, or a credential file by hand, and never create an automation with a raw subscribe_* call that skipped the review. For new automations, the only finish path is the automate skill's reviewed draft, approval, and /automations handoff.
Do not enable either automation until the thread-safety test passes after the /automations create or edit handoff.
8. Test thread safety
Use a test channel or a harmless test report.
Before testing, confirm that the target repository's .pi/settings.json, .pi/automations/benny/, and every referenced secret-free configuration file are committed on the branch used by the automation checkout. Confirm that both live prompts point at their exact committed operational files. If any check fails, stop. Tell the user that the automation cannot be enabled yet.
Verify:
- Triage stores the root
thread_tsand posts exactly one verdict as a reply. - The verdict contains one configured marker.
- Repro accepts the marker only from the configured triage identity.
- Repro keeps the same immutable source coordinates.
- No source-channel root message appears.
- A delegated worker cannot use any Slack write action.
- Missing coordinates, a deleted parent, or a failed preflight produces no post and no tracker issue.
Enable normal traffic only after all seven checks pass.
04 同仓库更多 Skills
plant
暂无简介
vitest-best-practices
Use when writing or reviewing Vitest tests, fixing flaky or slow tests, debugging failures, structuring suites, writing assertions (toBe vs toEqual vs toStrictEqual, asymmetric matchers, expect.soft, expect.poll, vi.waitFor), testing async code, setup/teardown hooks, test context and fixtures (test.extend, aroundEach), mocking (vi.fn, vi.spyOn, vi.mock, vi.hoisted, vi.when, classes), fake timers and dates, globals and env stubs, network mocking with MSW, file system mocking, snapshots, type testing (expectTypeOf), DOM environments (jsdom, happy-dom), Browser Mode, component testing (React, Vue, Svelte), benchmarking, database/integration tests, test tags and filtering, configuration and projects (monorepos), parallelism and performance, coverage, reporters, CI sharding, or migrating from Jest or Vitest 4. Targets Vitest 5.x.
plant-run
A planted skill whose blocks compile; one test fails, one is compile-only, and one never runs.
nope
A planted skill whose every file holds a mistake the gate must report, one class of mistake per block.
compose-robolectric-best-practices
Use when writing or reviewing Jetpack Compose UI tests that run on the JVM with Robolectric, fixing flaky or slow Compose tests, debugging test failures, structuring suites, choosing finders and semantics matchers (onNodeWithText, onNodeWithTag, hasX, useUnmergedTree), assertions, actions and gestures (performClick, performTextInput, performTouchInput, performScrollTo), synchronization (waitForIdle, waitUntil, mainClock, the v2 StandardTestDispatcher test APIs), JUnit rules and fixtures, screen robots, fakes and test data, ViewModel and StateFlow screens, navigation (Navigation Compose, Navigation 3), lists and scrolling, text fields and forms, dialogs and popups, animations and the test clock, configuration changes (qualifiers, dark mode, locale, RTL, font scale, state restoration), View interop, activities, intents, permissions and back press, screenshot tests with Roborazzi, accessibility checks, Robolectric configuration (@Config, sdk, qualifiers, looper and graphics modes), CI, performance, coverage, or migrating from the v1 Compose test APIs. Targets Compose BOM 2026.09 (ui-test 1.12) and Robolectric 4.17.
create-skill
Create Cursor Agent Skills. Use when authoring a new skill or asking about SKILL.md structure.