์Šคํ‚ฌ github-issue-creator
๐Ÿ“ฆ

github-issue-creator

์•ˆ์ „

Create GitHub Issues from Raw Notes

Stop wrestling with unstructured bug reports. Transform voice notes, error logs, and messy descriptions into professional GitHub issues that developers can actually use.

์ง€์›: Claude Codex Code(CC)
๐Ÿฅ‰ 74 ๋ธŒ๋ก ์ฆˆ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"github-issue-creator" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Error: PERMISSION_DENIED when publishing to Teams channel. Code: 403. Was working yesterday.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Summary: 403 PERMISSION_DENIED error when publishing to Teams channel
  • Environment: Copilot Studio Teams integration
  • Expected: Agent publishes successfully to Teams channel
  • Actual: Returns PERMISSION_DENIED with code 403
  • Impact: High - Blocks Teams integration, regression from previous working state

"github-issue-creator" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. so I was trying to deploy the agent and it just failed silently no error nothing the workflow ran but then poof gone from the list had to refresh and try again three times

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Summary: Agent deployment fails silently - no error displayed, agent disappears from list
  • Reproduction: Deploy agent, observe workflow completes, check agent list
  • Expected: Agent appears in list with deployment status
  • Actual: Agent disappears from list with no error message
  • Impact: High - Blocks agent deployment workflow, no feedback on failure cause

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „
v1 โ€ข 2/25/2026

Static analyzer flagged 21 patterns as potential security issues, but all are false positives. The SKILL.md file contains only markdown documentation and prompt templates - no executable code. Backtick characters are used for markdown code blocks and inline code formatting, not shell command execution. No cryptographic functions or external command execution present.

1
์Šค์บ”๋œ ํŒŒ์ผ
143
๋ถ„์„๋œ ์ค„ ์ˆ˜
0
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
1
์ด ๊ฐ์‚ฌ ์ˆ˜
๋ณด์•ˆ ๋ฌธ์ œ๋ฅผ ์ฐพ์ง€ ๋ชปํ–ˆ์Šต๋‹ˆ๋‹ค
๊ฐ์‚ฌ์ž: claude

ํ’ˆ์งˆ ์ ์ˆ˜

38
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
50
์ปค๋ฎค๋‹ˆํ‹ฐ
100
๋ณด์•ˆ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Quick Bug Documentation

Dictate bug details while reproducing an issue, then have them instantly formatted as a proper GitHub issue.

Error Log Analysis

Paste raw error messages and stack traces to generate structured issue reports with proper formatting.

Incident Response

Document production incidents quickly by describing what happened, then generate formal issue reports for tracking.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Basic Error Report 
I got this error: [paste error message]. Create a GitHub issue for this bug.
Voice Dictation 
Convert this voice note into a GitHub issue: [paste transcribed voice message describing a bug]
Detailed Incident 
Create a GitHub issue from this incident: Product: [name], Error: [details], Steps: [what you did], Expected: [what should happen], Impact: [who is affected]
Regression Report 
Document this regression as a GitHub issue: Feature [name] was working [when]. Now [current behavior]. Error: [any error messages]. This blocks [workflow].

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Include specific error codes and messages in the Error Details section for faster debugging
  • Clearly separate expected vs actual behavior to help developers understand the gap
  • Assign severity levels honestly based on user impact, not personal frustration

ํ”ผํ•˜๊ธฐ

  • Vague descriptions like it does not work without specific details about what is broken
  • Mixing multiple unrelated bugs in one issue - create separate issues instead
  • Speculating about root causes in the issue body instead of sticking to observed facts

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

Does this skill create issues directly on GitHub?
No, it generates markdown files in your repository issues directory. You can review and manually create the GitHub issue or use other tools to automate the upload.
What if I do not have all the environment details?
The skill uses placeholders like PROJECT_NAME or REGION for missing information. Fill these in when you know them.
Can it analyze my code to verify the bug?
No, this skill formats reported issues but does not test, debug, or verify code behavior.
How does it determine severity levels?
Severity is based on impact: Critical for service down or data loss, High for blocked features, Medium for impaired functionality with workarounds, Low for minor issues.
Can it handle screenshots or images?
It references images inline with placeholder descriptions. You will need to attach actual screenshots separately.
Is this skill safe to use with sensitive code?
Yes, it generates local markdown files and does not send data to external services. Always review generated content before sharing.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

sickn33

๋ผ์ด์„ ์Šค

MIT

๋ฆฌํฌ์ง€ํ† ๋ฆฌ

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/github-issue-creator

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md