Skip to content

getnao/sylph / .claude/skills/create-issue

create-issue

Verified

Create GitHub Issue

Standard process for creating well-structured GitHub issues. Use for bugs, feature requests, and tasks.

MCP connectors

ConnectorPurpose
GitHubCreate 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

LabelWhen to use
bugSomething is broken
featureNew functionality request
enhancementImprovement to existing feature
docsDocumentation change needed
good first issueSimple, well-scoped, good for new contributors
priority:highBlocks users or causes data issues
priority:lowNice to have, no urgency
needs-triageNeeds review before prioritization
customer-reportedCame from customer feedback

Process

  1. Check for duplicates - search existing issues before creating
  2. Use the right template - bug report or feature request
  3. Add labels - at least one type label and one priority label
  4. Link related issues - reference with #issue-number if related
  5. 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 chart
  • docs: 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:

  1. If the CAO edits an issue title, body, or labels before posting, note the pattern
  2. 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
  3. Update product/_insights.md with patterns: which issue formats get the fastest triage, which label conventions the team actually uses
  4. If an issue template works particularly well, save it to product/_examples/ as a reference
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: 196kUpdated Claude CodeCodexVerifiedInstall
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: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
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: 192kUpdated Claude CodeCodexVerifiedInstall