Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

github-pr-cull

Sterne8

Forks4

Aktualisiert15. Juni 2026 um 17:32

Triage the open/unmerged pull requests on eoffermann/BigBlueBam — assess each PR's approach against the code, then merge / revise / close with a documented rationale, under the same Eddie-sign-off gate as the issue cull. Invoked as the Phase 7 follow-up of github-issue-cull, or standalone when asked to clear out stale PRs. Records into the same dated dossier.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

eoffermann

eoffermann/BigBlueBam

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	github-pr-cull
description	Triage the open/unmerged pull requests on eoffermann/BigBlueBam — assess each PR's approach against the code, then merge / revise / close with a documented rationale, under the same Eddie-sign-off gate as the issue cull. Invoked as the Phase 7 follow-up of github-issue-cull, or standalone when asked to clear out stale PRs. Records into the same dated dossier.

GitHub PR cull — assess → decide → (gated) merge or close

You are clearing the open pull requests on eoffermann/BigBlueBam. For each PR, decide one of: merge (sound + current), revise (right idea, needs work — do the work on the PR's branch or a follow-up), or close (superseded, wrong approach, or obsolete) — every decision documented with its reason. Same hard gates as github-issue-cull: nothing reaches stable without Eddie's go, changes stay least-disruptive, and fixes are proven on the local stack before they're called done.

Phase 0 — Enumerate

gh pr list --repo eoffermann/BigBlueBam --state open --limit 200 --json number,title,url,headRefName,baseRefName,author,createdAt,updatedAt,isDraft,mergeable,labels. For each, pull the diff + linked issue: gh pr view <n> --json ... and gh pr diff <n>. Append a ## PR #<n> — <title> section to the current issue_mitigations_<YYYYMMDD>.md (create it if running standalone).

Phase 1 — Evaluate each PR (delegate)

Spawn pr-evaluator per PR with the diff, the PR description, and any linked issue. It returns: what the PR claims to do, whether the diff actually does that and addresses the real root cause, correctness/risk concerns (file:line), whether it still applies to current main (drift/conflicts), test coverage, and a recommendation — merge / revise / close — with reasons. Record it.

Phase 2 — Act on the recommendation

Merge candidate: rebase/retarget onto main if needed, run typecheck + the relevant live smoke locally, then queue it for the Phase-3 sign-off (do NOT merge yet).
Revise: push the minimal fixes to the PR's branch (or a follow-up branch), re-run the smoke, comment on the PR explaining what changed, then queue it.
Close: comment with the rationale (superseded by <commit/issue>, obsolete, or approach rejected because …) and queue the close for sign-off. Don't close a contributor's PR silently.

Phase 3 — Report & ship (gated)

Summarize for Eddie: per PR — claim, verdict, action, confidence. Stop for his go. On sign-off: merge approved PRs to main, promote main→stable (FF) and monitor the Railway rollout (per [[feedback_stable_promotion_monitor]]), close the close-list PRs with their comments, and delete merged branches.

Done means

Every open PR has a dossier entry, a posted disposition, and is either merged (past sign-off), revised-and-queued, or closed with a reason. Nothing reached stable without Eddie's explicit go.

Mehr aus diesem Repository

gleiches Repository

docs-book-author

eoffermann/BigBlueBam

Assemble or extend the printable, textbook-style BigBlueBam manual (the DOCX and PDF offered from /docs). Use when asked to build the downloadable manual, add or refresh a chapter, write chapter intros/callouts/quizzes, or change the book's design. Produces a bold, colorful, per-app book from the SAME content as the web docs, then converts to PDF.

2026-06-218

screenshot-capture

eoffermann/BigBlueBam

Produce realistic, fully-populated screenshots of any view in the BigBlueBam suite from declarative YAML recipes — auth, content seeding, deterministic capture, and a manifest. Use when creating/updating docs or marketing-site assets, or refreshing captures after a UI change.

2026-06-178

github-issue-cull

eoffermann/BigBlueBam

Triage, investigate, mitigate, and (after sign-off) resolve the open GitHub issues on eoffermann/BigBlueBam. Builds a dated issue_mitigations_<YYYYMMDD>.md dossier, posts an "investigating" acknowledgement on each issue, implements least-disruptive fixes on per-issue branches, has an independent agent re-verify each fix from the code alone, reports to Eddie, and on his go-ahead merges main→stable + closes addressed PRs. Use when asked to work through / cull / clear the repo's open issues. Pairs with the github-pr-cull companion skill for the unmerged-PR pass.

2026-06-158

suite-help-system

eoffermann/BigBlueBam

Standard for building and maintaining BigBlueBam's unified in-app help system: a "(?)" Help Center launched from every app's top bar (TOC, search, index, cross-references) sourced from docs/apps/<app>/help.md, plus right-click "Help: <element>" deep-links on UI elements that the help docs reference. Use when building, extending, or updating the help feature for any app.

2026-06-158

help-doc-authoring

eoffermann/BigBlueBam

Standard for authoring and reviewing BigBlueBam per-app help.md files. Use whenever writing, structuring, or checking a help document for any app in the suite. Defines the canonical template, the User Story format, source priority, writing conventions, and the acceptance checklist.

2026-06-148

ui-debug

eoffermann/BigBlueBam

Debug a UI feature by writing its expected-behavior user story, then walking the full stack top-down — UI control → handler → hook → API route → backend logic → data effect — and smoke-testing it live on the local dev stack with self-cleaning test data. Use when a UI element "does nothing", silently fails, or "looks wired but isn't", and before declaring ANY UI feature done. Nothing is "done" until the UI is proven to call real logic and that logic is proven to do what the story says.

2026-06-148

name	github-pr-cull
description	Triage the open/unmerged pull requests on eoffermann/BigBlueBam — assess each PR's approach against the code, then merge / revise / close with a documented rationale, under the same Eddie-sign-off gate as the issue cull. Invoked as the Phase 7 follow-up of github-issue-cull, or standalone when asked to clear out stale PRs. Records into the same dated dossier.

GitHub PR cull — assess → decide → (gated) merge or close

Phase 0 — Enumerate

Phase 1 — Evaluate each PR (delegate)

Phase 2 — Act on the recommendation

Merge candidate: rebase/retarget onto main if needed, run typecheck + the relevant live smoke locally, then queue it for the Phase-3 sign-off (do NOT merge yet).
Revise: push the minimal fixes to the PR's branch (or a follow-up branch), re-run the smoke, comment on the PR explaining what changed, then queue it.
Close: comment with the rationale (superseded by <commit/issue>, obsolete, or approach rejected because …) and queue the close for sign-off. Don't close a contributor's PR silently.

Phase 3 — Report & ship (gated)

Done means

Every open PR has a dossier entry, a posted disposition, and is either merged (past sign-off), revised-and-queued, or closed with a reason. Nothing reached stable without Eddie's explicit go.