Menü
Pull user bug reports from the bindery Discord and convert them to GitHub issues
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.
| name | discord-reports |
| description | Pull user bug reports from the bindery Discord and convert them to GitHub issues |
| disable-model-invocation | true |
Collect and process Discord bug reports. Access details (bot token location, guild/channel IDs) are in CLAUDE.local.md — never print the token.
GET /channels/{id}/messages?limit=50, header Authorization: Bot <token>, Discord API v10. Use curl — Discord's Cloudflare blocks Python urllib. Default lookback: since the last run noted in memory, else 7 days; $ARGUMENTS overrides.gh issue list --search). If a report matches an open issue, note the +1 instead of filing a duplicate.gh issue create, then draft a short reply for the Discord thread pointing to the issue (tone rules in CLAUDE.local.md). Post replies only after I approve them.Basierend auf der SOC-Berufsklassifikation
Analyze and fix a GitHub issue end-to-end, producing a PR
Sweep open issues and PRs, categorize, and propose a work queue
Use when picking a branch name, staging files, or writing a commit message — covers branch conventions, the project's Conventional Commits format with the scope vocabulary observed in history, and the documentation-update gate that fires before every commit (`docs/*`, `README.md`, godoc, Helm values).
Use when opening or updating a pull request, responding to review, or filing a GitHub issue — covers the PR body skeleton matched to recent merged PRs, draft → ready → squash mechanics, rebase-vs-merge policy, and the issue-template routing (`bug_report.yml` / `feature_request.yml`, blank issues disabled).
Use when deciding whether to run an out-of-process test suite (real binary or live instance) — picks between `make smoke`, `make abs-contract`, and `make predeploy-smoke` after the unit suite passes but you've changed handler wiring, scheduler jobs, downloader integration, ABS imports, or anything that boots the binary. For the routine pre-PR matrix (lint / vet / test / typecheck / build) see the `testing` skill.
Use when cutting a release — composing the `## [vX.Y.Z]` `CHANGELOG.md` section, picking the version bump, and walking commits since the last tag. Authoring only; the maintainer pushes the tag (which triggers GoReleaser + provenance signing) and the deploy bot auto-bumps Helm `values.yaml`.
