gh-issue-push

Create a GitHub issue in the current repository.

الانتقال إلى التثبيت

المستودع: petar-djukic/coding-skills
آخر نشاط في المصدر: ٢٦ يوليو ٢٠٢٦ في ٠٣:٣١
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٢
التفرعات: ٠

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

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

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/petar-djukic/coding-skills --skill gh-issue-push

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

gh-issue-push command

Apply this command workflow. Treat any text after its invocation as the command input.

Create a GitHub issue in the current repository.

Input

$ARGUMENTS

Steps

Detect the repo: run gh repo view --json nameWithOwner -q .nameWithOwner and use the result as <owner>/<repo> for all gh commands.

Determine type from the input: keywords like "bug", "fix", "broken", "crash" → bug; otherwise → enhancement.

Trace what the change touches. Before drafting, identify every file and field affected — not just the primary target. The executor will do exactly what the issue says and nothing else, so anything omitted will be missed.

Read the files involved to understand their structure.
grep for identifiers, names, or values being added, changed, renamed, or deleted. Search the full project, not just the obvious files.
For each hit, note the file path, the field or line, and what needs to change.
Check for status fields, summary fields, titles, index entries, cross-reference IDs, and out_of_scope references — these are the most commonly missed.

Draft a concise title and well-structured body.

Bug: problem, expected vs actual behavior, reproduction steps if provided.
Enhancement: description and acceptance criteria.
Both: include a "Files to Create/Modify" section listing every file. Under each file, list the specific fields or lines to change. If a value appears in multiple places in the same file, list each occurrence.
Code issues: include an Estimated LOC: line — the model's prediction of production lines of code (and test lines if separable). This is the estimate of record; the actual count is captured at completion by /gh-issue-pop, so estimation accuracy can be tracked over time.

Create the issue:

gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<bug|enhancement>"

Report the issue URL.

name	gh-issue-push
description	Create a GitHub issue in the current repository.

gh-issue-push command

Apply this command workflow. Treat any text after its invocation as the command input.

Create a GitHub issue in the current repository.

Input

$ARGUMENTS

Steps

Detect the repo: run gh repo view --json nameWithOwner -q .nameWithOwner and use the result as <owner>/<repo> for all gh commands.
Determine type from the input: keywords like "bug", "fix", "broken", "crash" → bug; otherwise → enhancement.
Trace what the change touches. Before drafting, identify every file and field affected — not just the primary target. The executor will do exactly what the issue says and nothing else, so anything omitted will be missed.
- Read the files involved to understand their structure.
- grep for identifiers, names, or values being added, changed, renamed, or deleted. Search the full project, not just the obvious files.
- For each hit, note the file path, the field or line, and what needs to change.
- Check for status fields, summary fields, titles, index entries, cross-reference IDs, and out_of_scope references — these are the most commonly missed.
Draft a concise title and well-structured body.
- Bug: problem, expected vs actual behavior, reproduction steps if provided.
- Enhancement: description and acceptance criteria.
- Both: include a "Files to Create/Modify" section listing every file. Under each file, list the specific fields or lines to change. If a value appears in multiple places in the same file, list each occurrence.
- Code issues: include an Estimated LOC: line — the model's prediction of production lines of code (and test lines if separable). This is the estimate of record; the actual count is captured at completion by /gh-issue-pop, so estimation accuracy can be tracked over time.

Create the issue:

gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<bug|enhancement>"

Report the issue URL.

gh-issue-push

معلومات المصدر

خيارات التثبيت

مراجعة ملفات المصدر

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

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

gh-issue-push command

Input

Steps

gh-issue-push command

Input

Steps