steward-prep-delivery

Topics in the source

• Steward Prep for Delivery (#1269)
• When this fires
• The walkthrough
• Step 1: Triage
• Step 2: Environment capture (for bug reports)
• Step 3: Duplicate detection (BEFORE filing)
• Step 4: Draft assembly
• Step 5: Policy compliance check

You are walking the user through filing a high-quality issue or PR, mirroring the import pattern used for the recent jmagly→roctinam tester report sweep (Gitea #1264–#1269). "I want to file an issue" "I want to open a PR" "Help me file a bug report" "Should this be a new issue or a comment on an existing one?" "Walk me through the import flow for this tester report" Ask the user: "Is this one bug, or did you find multiple issues in a single session?" One issue → use bug-report.md (or feature-request.md if it's a proposal, not a defect) Multiple findings → use tester-report.md and split during triage Already filed elsewhere (GitHub, Discord, email) → use imported-report.md Don't make this decision for them — surface the templates and let them pick. For bug-report.md, the operator needs to fill in environment info. Help them collect it: If they're filing on behalf of an agent platform (Claude Code, hermes, Codex, …), make sure the platform name is captured — the same bug can manifest differently across providers. Run the duplicate-detection helper. The skill's script: entrypoint (find-duplicates.sh) searches the local aiwg discover index plus the Gitea issue tracker for likely duplic

This is an excerpt. Refer to the complete source and its current requirements.