# Create Developer-Ready GitHub Issues

Unstructured bug reports slow triage and omit critical details. This skill converts logs, notes, screenshots, and dictation into structured GitHub issue markdown.

## Install

```bash
npx skillstore add sickn33/github-issue-creator
```

## Metadata

- Status: approved
- Slug: sickn33-github-issue-creator
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4f56392871b3d40e68b3d56fc03e0ff9ec16827a6d3e2deba88f22bf43673acc
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/github-issue-creator
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/sickn33-github-issue-creator
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-github-issue-creator/manifest

## Capabilities

- Organizes unstructured notes, logs, screenshots, and dictation into consistent issue sections.
- Drafts summaries, environments, reproduction steps, expected behavior, actual behavior, errors, impact, and context.
- Assigns issue severity using explicit impact definitions.
- Replaces potentially sensitive values with descriptive placeholders.
- Creates dated Markdown issue files under the repository issues directory.

## Use Cases

- Convert Support Notes: Turn customer reports and support notes into structured issues for engineering triage.
- Standardize Test Defects: Transform test observations, screenshots, and error output into consistent defect reports.
- Document Production Failures: Capture incident symptoms, impact, environment details, and reproduction evidence for follow-up work.

## Prompt Templates

### Create an Issue from a Note

```
Create a GitHub issue from this bug note: [NOTE]. Use placeholders for sensitive data and ask about missing required details.
```

### Structure an Error Report

```
Turn this error log and context into an issue: [ERROR LOG] [CONTEXT]. Include environment, reproduction steps, expected behavior, actual behavior, and impact.
```

### Combine Multiple Evidence Sources

```
Create one issue from these notes, screenshots, and logs: [EVIDENCE]. Separate confirmed facts from inferred details and list unanswered questions.
```

### Draft a Triage-Ready Regression

```
Draft a regression issue from [EVIDENCE]. Compare previous and current behavior, assess impact, redact sensitive values, and propose a collision-safe filename.
```

## Limitations

- Does not submit issues to GitHub or call GitHub APIs.
- Cannot validate reproduction steps or inferred environment details.
- References attachments but does not upload them.
- Requires clarification when essential evidence, permissions, or success criteria are missing.

## Best Practices

- Provide exact errors, timestamps, environment details, and observable behavior whenever available.
- Mark inferred details clearly and confirm them before filing the issue.
- Remove secrets and personal data while preserving useful diagnostic context.

## Anti Patterns

- Do not invent reproduction steps, environments, or causes that the evidence does not support.
- Do not include credentials, tokens, customer identifiers, or private repository details.
- Do not overwrite an existing issue file without explicit confirmation.

## Security Audit

- Audited at: 2026-07-23T23:58:41.115\+00:00
- Summary: All 13 static findings are false positives caused by Markdown code fences and inline code spans. No Ruby or shell command execution appears in SKILL.md. The skill requests repository file creation, creating a limited filesystem write risk.

## Stats

- Views: 117
- Downloads: 11
- Favorites: 0
- Popularity score: 0