Skip to content

EricTechPro/super-board / skills/super-collect

super-collect

Verified

Find problems in one project, verify each, write one findings doc and hand it to Matt Pocock's /to-spec then /to-tickets; 1–5 tickets go to /implement-spec, 6+ to the super-board Backlog (no /to-spec or /to-tickets installed → files straight into Backlog). Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier first. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors".

FileKindSize
README.mdmarkdown3.0 KB
SKILL.mdskill md17.3 KB
references/correction-prevention.mdmarkdown2.7 KB
references/scheduled-intake.mdmarkdown4.0 KB
scripts/collect_common.pyexecutablescript3.5 KB
scripts/collect_custom.pyscript14.6 KB
scripts/collect_handoff.pyexecutablescript7.2 KB
scripts/collect_posthog.pyexecutablescript16.4 KB
scripts/collect_prs.pyexecutablescript4.7 KB
scripts/collect_sentry.pyexecutablescript10.3 KB
scripts/super-collect-file.shexecutablescript14.7 KB

references/correction-prevention.md

View on GitHub
# Prevent a recurring mistake

For `prs` candidates, the finder and fresh verifier use the cited prior findings to name
one shared boundary, the actual failing input/action and what allowed it. Group by that
cause. A one-off finding remains outside recurrence intake.

## Choose the correction

Prefer the strongest appropriate correction:

1. Remove the invalid path/operation, or route callers through an already adequate owner.
2. Express the invariant in a type/schema when it fits.
3. Guard the boundary with lint/runtime checks and an actionable error when static expression
   cannot cover it.
4. Cover the remaining possible mistake with a behavior regression witness.
5. Reserve prose for judgment that cannot appropriately be enforced.

Stop where the correction fits. These are preferences, not five required mechanisms.
Choose an existing owner before inventing a helper; add no dependency, abstraction or custom
linter solely to climb the list. The proposed correction must address the permitting boundary,
not merely repeat a reminder or patch another call site.

## Propose proof, then verify delivery

Keep the [ticket sections](../../super-board/references/ticket-format.md). Context names the
boundary and failing input/action; Evidence cites the prior PR/comment/finding and retained
witness source. Fix states intended prevention in 1–3 lines. A behavioral AC requires:

- The actual prior bad witness fails against old behavior for the reported invariant.
- That same witness passes after correction.
- A behavior-preserving refactor still passes, without asserting filenames or helper names.

Use the worker's [test gates](../../super-build/references/decision-policy.md#skill-map)
for placement and correct red. Missing dependencies, selectors, setup errors and unrelated
timeouts do not prove the incident. If the actual witness cannot be reconstructed, say so
and leave its proof/AC unverified. An invented sample cannot replace historical proof.

Collect proposes this AC; it does not implement or execute the product regression. The fresh
verifier checks the source and current applicability, then normal dedupe and user curation
file only into Backlog. Canned fixtures demonstrate intake behavior, not a live incident.

## Calibration authority

Apply the same correction preference to a completed run's bounded lessons. Product changes
in ownership, types, schemas, guards or tests remain proposals for ordinary verified,
curated Backlog intake. Calibration may edit only its explicit existing canonical SKILL.md
allowlist using current-run evidence. Follow the host's
[calibration scope](../../super-board/references/calibration.md#delegate-the-installed-skill)
and diff inspection; a stronger product mechanism does not expand edit authority.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall