getnao/sylph / .claude/skills/create-issue
create-issue
VerifiedCreate GitHub Issue
Standard process for creating well-structured GitHub issues. Use for bugs, feature requests, and tasks.
MCP connectors
| Connector | Purpose |
|---|---|
| GitHub | Create and label issues |
Bug report template
## Problem
[Clear description of what's broken. Include steps to reproduce.]
1. Step one
2. Step two
3. Observe: [what happens]
## Expected behavior
[What should happen instead]
**Environment**: [browser, OS, version, relevant config]
Feature request template
## Problem
[What user problem does this solve? Who is affected?]
## Expected behavior
[What the feature should do, from the user's perspective]
## Notes
[Optional: technical considerations, related issues, mockups]
Labels
| Label | When to use |
|---|---|
bug | Something is broken |
feature | New functionality request |
enhancement | Improvement to existing feature |
docs | Documentation change needed |
good first issue | Simple, well-scoped, good for new contributors |
priority:high | Blocks users or causes data issues |
priority:low | Nice to have, no urgency |
needs-triage | Needs review before prioritization |
customer-reported | Came from customer feedback |
Process
- Check for duplicates - search existing issues before creating
- Use the right template - bug report or feature request
- Add labels - at least one type label and one priority label
- Link related issues - reference with
#issue-numberif related - Assign - only if the assignee is clear; otherwise leave unassigned
Title format
- Bug:
[component] Short description of what's broken - Feature:
[component] Short description of desired behavior - Docs:
docs: Short description of what needs updating
Examples:
[API] Query timeout on large datasets[Dashboard] Add date range filter to usage chartdocs: Update authentication setup guide
Guardrails
- No PII - scrub customer names, emails, and company names from all issue content
- One issue per problem - no omnibus issues covering multiple bugs
- No Impact section - keep body to Problem + Expected behavior only
- No confidential data - no API keys, credentials, or internal URLs in issues
- Don't close issues - only the CAO or the assignee closes issues
Self-improvement
After the CAO reviews created issues:
- If the CAO edits an issue title, body, or labels before posting, note the pattern
- If her edits reveal a preference for how problems are framed, bug reports are structured, or priorities are assigned, update the Templates or Labels sections
- Update
product/_insights.mdwith patterns: which issue formats get the fastest triage, which label conventions the team actually uses - If an issue template works particularly well, save it to
product/_examples/as a reference
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |