القائمة
Create a new GitHub issue for a feature, bug, or chore. Use when you have an idea, bug report, or task that needs a GitHub issue with analysis and solution options.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | gh-issue |
| description | Create a new GitHub issue for a feature, bug, or chore. Use when you have an idea, bug report, or task that needs a GitHub issue with analysis and solution options. |
| allowed-tools | Bash(gh issue create:*), Glob, Grep, Read, WebSearch |
Feature/Bug/Chore idea: $ARGUMENT$
Ask me questions about anything unclear:
Wait for my answers before continuing.
Create an issue with this structure:
What problem does this solve? What are current limitations?
What specific benefits will users get? Give concrete examples.
[Same format as Option 1]
Which option and why
Show me the complete issue draft and ask: "Is this ready to create? Any changes needed?"
Wait for my approval.
After approval, run:
gh issue create --title "[Feature/bug/chore] YOUR_TITLE_HERE" --body "YOUR_ISSUE_CONTENT_HERE"
Tell me the issue number and URL when done.
Key improvements:
1. **Removed nested markdown** - The triple backticks inside the prompt were likely causing parsing issues
2. **Simplified structure** - Clearer step-by-step format
3. **Separated commands** - Split the issue creation and project assignment into two commands (gh CLI doesn't support --project flag in create command)
4. **Clearer placeholders** - YOUR_TITLE_HERE and YOUR_ISSUE_CONTENT_HERE are more obvious to replace
5. **Removed complex formatting** - Simplified the markdown structure to avoid parsing conflicts
6. **Direct instructions** - More imperative language that's easier to follow
Create git commits from current changes using Conventional Commits format. Use when ready to commit staged or unstaged changes.
Generate a branch name from current changes and create it if on main. Use when starting new work and need a properly named feature branch.
Create a pull request from the current branch with quality checks. Use when changes are ready for review, after committing.
Interactive guide for creating new Claude skills with proper structure, frontmatter, and trigger conditions. Use when building a new skill, scaffolding a SKILL.md, or need guidance on skill best practices.
Run Prisma generate, lint (auto-fix), typecheck, and tests; iterate until clean, summarize results. Use when CI is failing or before pushing to verify the repo is clean.
Merge current feature branch into fresh staging branch with conflict resolution. Use when ready to deploy a feature branch to the staging environment.