Menu
Raise a detailed, structured issue on GitHub. Gathers context, builds reproduction steps, expected outcomes, and acceptance criteria.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start work on a new GitHub issue. Fetches issue details, generates standard branch names, and sets up the branch.
Generate a detailed, high-depth pull request body and create/update a PR on GitHub. Gathers workspace changes, updates the PR body dynamically, and posts update comments to capture a historical paper trail.
Monitor the CI checks status of a Pull Request on GitHub, parse logs on failure, and address any non-passing tests.
Finish work on the current issue branch. Runs quality gates (formatting, linting, tests), handles uv.lock version drift, and pushes to remote.
| name | raise-issue |
| description | Raise a detailed, structured issue on GitHub. Gathers context, builds reproduction steps, expected outcomes, and acceptance criteria. |
Standardized procedure to generate and raise a high-quality, deeply detailed issue on GitHub for this project.
Analyze the problem or requirement: Collect all relevant details:
Generate a detailed, structured description: Determine whether the issue is a Bug or a Feature/Enhancement, and choose the corresponding structure.
## Problem
[Detailed description of what is failing and why it is wrong/suboptimal. Include any traceback error logs here.]
## Steps to reproduce / Reproduction
\`\`\`bash
[Exact shell command or python sequence to trigger the bug]
\`\`\`
## Expected behaviour
[Explain what the CLI/application should ideally output or do.]
## Actual behaviour
[Explain what the CLI/application is currently outputting or doing.]
## Suspected Cause (optional)
[If a specific file, class, function, or recent commit is suspected, reference it here.]
## Description / Problem
[High-level explanation of the new feature, why it is beneficial, and what user problem it solves.]
## Proposed Solution
[Explain how it should be implemented, listing CLI flags, configuration parameters, and code structure.]
## Examples
\`\`\`bash
# Show command examples if applicable
breakfast -o spec --new-flag
\`\`\`
## Acceptance Criteria
- [ ] [Feature behaves as expected under condition A]
- [ ] [Configuration overrides CLI values correctly]
- [ ] [Updated manual pages in docs/manual/ reflect changes]
- [ ] [make format && make lint && make test all pass]
Verify the Title format: Ensure the issue title is clean and descriptive.
feat: or fix:) in GitHub issue titles, as these are reserved for commits and PRs. Keep the title imperative and natural.Create the issue using the GitHub CLI (gh):
Execute the gh issue create command using the derived title and generated body:
gh issue create --title "<title>" --body "<body>"
(If the GitHub CLI is not authenticated or available, output the formatted title and body so the user can easily copy and paste them into the GitHub web interface).
Confirm to the user: Report the generated issue URL, issue number, and a summary of the details.