mirror of https://github.com/cursor/plugins.git synced 2026-09-14 20:00:00 +08:00

Files

T

lauren 0452e08a31 pstack: add Benny issue automation pack (#137 )

## Summary
- add a dormant Benny source pack for thread-only issue triage and evidence-backed repro and fix workflows
- copy the pack into target repositories so live automations read committed files directly without exposing Benny as slash skills
- keep pstack enabled only for shared workflow dependencies and preserve user-owned configuration outside pack refreshes

## Test plan
- [x] `node scripts/validate-plugins.mjs`
- [x] validate the manifest exposes only `./skills/`, direct operational paths, Markdown links, JSON and YAML examples, frontmatter, and unique skill names
- [x] scan the branch for discovery contradictions, private names, IDs, credentials, endpoints, and local plugin paths
- [x] run `git diff --check origin/main...HEAD` and review the full branch diff

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Documentation and dormant automation sources only; no runtime code paths in the plugin. Operational risk applies only after users enable automations with Slack, tracker, and repo write access in their own repos.
> 
> **Overview**
> **Bumps pstack to 0.10.0** and documents a new **dormant Benny pack** under `automations/benny/` for Slack-driven issue workflows (not added to the plugin slash-skill manifest).
> 
> The pack defines **two coordinated Cursor automations**: **triage** (classify reports, cause-aware routing, tracker dedupe, single thread reply with `[benny:bug]` / `[benny:performance]` / `[benny:other]`) and **repro/fix** (wait for trusted triage markers, double UI repro via a configured control adapter, verify existing PRs, optional bounded fix with **draft-only** PRs). Operational behavior lives in committed `SKILL.md` files with strict thread-only Slack rules, fail-closed gates, and coordinator-only posting.
> 
> **Setup** is agent-driven via `FOR_AGENTS.md` and `setup-benny`: merge the pack into the target repo at `.cursor/automations/benny/`, enable **pstack** in `.cursor/settings.json` for shared skills (`how`, `why`, `tdd`, `unslop`, principles), keep user config outside the pack, and wire live automations through `/automate` (or editor updates for existing ones). Templates cover configuration, routing, feature maps, control-adapter contract, and prompt shims.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1028dd3a69. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

2026-06-23 21:43:34 -07:00

7.3 KiB

Raw Permalink Blame History

benny automation intent

what i want to automate

i want two cursor automations that work together in one slack issue channel.

automation 1: triage issue reports

trigger: when someone posts a new top-level report in my configured source slack channel, i want this automation to start on that report and keep its original thread coordinates.
behavior: i want it to read the thread and attachments, classify the report as a bug or performance issue, feature request, question or feedback, or reroute, and trace the likely owning layer before routing.
tracker: i want it to search my configured tracker for duplicates, update a confident duplicate, and create a ticket only for a clear net-new bug.
tools: i want slack thread read and reply access, my configured tracker integration, and my optional routing map.
outcome: i want exactly one reply in the source thread with a short verdict and [benny:bug], [benny:performance], or [benny:other]. a bug or performance marker may include the tracker url.
boundary: i never want this automation to post a root message in the source channel.

automation 2: reproduce and fix confirmed bugs

trigger: i want this automation to start from the same new top-level report, or another supported trigger chosen during setup, then wait for the trusted triage marker in the original thread.
gates: i want it to stop when someone clearly owns the fix. if an existing pull request or merged commit may fix the report, i want verification instead of a competing change.
behavior: i want it to use my configured control adapter and feature map, reproduce the exact symptom twice through the real ui, and capture screenshots, video, and a read-only state cross-check.
fix: i want it to verify existing pull requests without authoring over them. after a confirmed repro, it may attempt one bounded root-cause fix, use tdd when the test is cheap, smoke the blast radius, and open a draft pull request only when before-and-after proof passes.
tools: i want slack thread read and reply access, repository and history access, draft pull request creation, my configured tracker, and my control adapter.
outcome: i want evidence and a verified result in the source or optional operations threads, plus an optional draft pull request. updates should be concise.
boundary: i never want this automation to post a root message in the source channel.

shared rules

i want the source channel and root thread coordinates to stay immutable for the whole run.
i treat utility and debug bots as evidence, not delegation or fix ownership.
i allow subagents to help, but they cannot post to slack or receive slack credentials.
i want this entire pack committed at .cursor/automations/benny/ in the target repository. its SKILL.md files are direct automation instructions, not registered plugin skills.
i want pstack enabled through the target repository's committed .cursor/settings.json only for shared dependencies such as how, why, tdd, unslop, and the required principle skills.
i want each live automation prompt to read its committed operational file directly. i do not want plugin cache paths, copied excerpts, or slash-skill discovery.
i keep user-owned configuration, feature maps, routing maps, and secrets outside .cursor/automations/benny/ so pack refreshes cannot overwrite them.
i want both automations to fail closed when channel coordinates, tracker access, the control adapter, or the feature map are missing or uncertain.
i want draft pull requests only. do not merge or deploy.

my configuration

source slack channel: <channel>
optional operations channel: <channel or none>
repository and default branch: <repo>, <branch>
tracker: <type, team, project, labels, intake status>
routing map: <path or none>
triage identity: <slack identity>
control skill: <configured skill or adapter>
feature map: <committed same-repo path outside the copied pack, or behavior to paraphrase>
models: <triage, reproduce, code, media review>
status emoji strings: <seen, reproducing, reproduced, blocked, fixing, failed, pull request opened>
budgets: <polling, verdict wait, follow-up, repro, rejection, fix>
optional bot token capability: <none, file download, or editable operations status>

start from configuration.example.yaml and feature-map.example.md. copy and fill them outside this pack, for example under .cursor/benny/. keep secret values in a secret manager or environment.

for the agent

the human enters setup by pointing cursor at this file. do not look for or invoke a discovered benny slash skill.

ask which repository will run the automations.
treat the directory containing this FOR_AGENTS.md as the source pack.
merge the entire source pack into <target-repository>/.cursor/automations/benny/.
preserve every destination-only file. never delete unrelated files or overwrite user-owned configuration, feature maps, or routing maps.
when an existing destination file at a source-managed path differs, review the diff and merge without discarding local edits. if ownership is ambiguous, stop and ask before replacing it.
verify that the copied FOR_AGENTS.md and skills/setup-benny/SKILL.md exist in the target repository.
read and follow .cursor/automations/benny/skills/setup-benny/SKILL.md directly from the target repository.

i want you to merge this entry into the target repository's .cursor/settings.json:

{
	"plugins": {
		"pstack": { "enabled": true }
	}
}

preserve every unrelated setting and plugin. preserve comments and valid jsonc syntax when the existing file uses jsonc.

i want verification from a fresh agent rooted in the target repository. confirm that pstack's how, why, tdd, unslop, and the principle skills used by benny resolve in project scope. do not count skills loaded from the current session or a user-scoped install.

if project-scoped plugins are unavailable or any shared dependency does not resolve, stop and explain what failed. do not add .cursor/automations/benny/skills/ to a plugin manifest or expect its files to appear in the slash-skill list.

tell me that .cursor/settings.json, .cursor/automations/benny/, and any referenced secret-free configuration must be committed before either automation is enabled. do not create or update an automation until i explicitly ask.

for first-time creation, use built-in /automate once for triage and once for repro and fix. complete the draft review, approval, readiness check, and Automations editor handoff for the first automation before starting the second.

paraphrase this intent and the finished configuration into each draft. the triage prompt must read and follow .cursor/automations/benny/skills/triage-issue-reports/SKILL.md. the repro prompt must read and follow .cursor/automations/benny/skills/reproduce-and-fix-issues/SKILL.md. use these repo-relative paths only after /automate confirms they are committed in the repository where the automation will run.

for existing automations, do not use /automate to inspect or update them. validate the configuration, then use the concise field checklist in the copied setup file so i can edit each automation directly in its editor. do not create duplicates.

7.3 KiB Raw Permalink Blame History