تشغيل أي مهارة في Manus بنقرة واحدة

raise-issue

النجوم٣

التفرعات٢

آخر تحديث٢ يونيو ٢٠٢٦ في ١٠:٣٦

Raise a detailed, structured issue on GitHub. Gathers context, builds reproduction steps, expected outcomes, and acceptance criteria.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

mrsixw

mrsixw/breakfast

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	raise-issue
description	Raise a detailed, structured issue on GitHub. Gathers context, builds reproduction steps, expected outcomes, and acceptance criteria.

Raise Issue Skill

Standardized procedure to generate and raise a high-quality, deeply detailed issue on GitHub for this project.

When to use this skill

Use this skill when you identify a bug, a required enhancement, or a new feature that does not have an active GitHub issue yet.
Remember: A GitHub issue MUST exist before any coding work begins. Always use this skill to create the issue first.

How to use it

Steps

Analyze the problem or requirement: Collect all relevant details:
- For bugs: exact error tracebacks, terminal output, reproduction commands, and conditions.
- For features: the proposed feature goals, user benefit, command-line flags, configuration structures, and CLI outputs.

Generate a detailed, structured description: Determine whether the issue is a Bug or a Feature/Enhancement, and choose the corresponding structure.

Structure for Bug Issues:

## 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.]

Structure for Feature/Enhancement Issues:

## 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.
- Important: Do not use conventional commit prefixes (like feat: or fix:) in GitHub issue titles, as these are reserved for commits and PRs. Keep the title imperative and natural.
- Example: "Support per-org scoped repo filter with org:filter syntax"
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.

المزيد من هذا المستودع

نفس المستودع

start-issue

mrsixw/breakfast

Start work on a new GitHub issue. Fetches issue details, generates standard branch names, and sets up the branch.

2026-06-093

raise-pr

mrsixw/breakfast

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.

2026-06-023

monitor-pr

mrsixw/breakfast

Monitor the CI checks status of a Pull Request on GitHub, parse logs on failure, and address any non-passing tests.

2026-06-023

finish-issue

mrsixw/breakfast

Finish work on the current issue branch. Runs quality gates (formatting, linting, tests), handles uv.lock version drift, and pushes to remote.

2026-06-013

Raise Issue Skill

Standardized procedure to generate and raise a high-quality, deeply detailed issue on GitHub for this project.

When to use this skill

Use this skill when you identify a bug, a required enhancement, or a new feature that does not have an active GitHub issue yet.

Remember: A GitHub issue MUST exist before any coding work begins. Always use this skill to create the issue first.

How to use it

Steps

Analyze the problem or requirement: Collect all relevant details:

For bugs: exact error tracebacks, terminal output, reproduction commands, and conditions.
For features: the proposed feature goals, user benefit, command-line flags, configuration structures, and CLI outputs.

Generate a detailed, structured description: Determine whether the issue is a Bug or a Feature/Enhancement, and choose the corresponding structure.

Structure for Bug Issues:

## 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.]

Structure for Feature/Enhancement Issues:

## 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.

Important: Do not use conventional commit prefixes (like feat: or fix:) in GitHub issue titles, as these are reserved for commits and PRs. Keep the title imperative and natural.
Example: "Support per-org scoped repo filter with org:filter syntax"

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.