From csdlc
Create a GitHub issue from the current context — bug reports, feature requests, tech debt items. Use when the user says "file an issue", "open a bug", "track this", "create an issue", or when a problem is discovered during a session that needs tracking.
npx claudepluginhub danhannah94/claymore-plugins --plugin csdlcThis skill uses the workspace's default tool permissions.
File an issue for: **$ARGUMENTS**
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
File an issue for: $ARGUMENTS
Create a well-structured GitHub issue from the current conversation context. Used for bug reports, feature requests, tech debt tracking, or anything that needs to be tracked in the project's GitHub repo.
Determine the target repo. Check in this order:
--repo flag in $ARGUMENTS (e.g., --repo danhannah94/foundry) — always winsDetermine the issue type. From context or ask:
Draft the issue. Format based on type:
Bug:
## Description
{What's broken, in one paragraph}
## Repro Steps
1. {Step to reproduce}
2. {Next step}
## Expected vs Actual
- **Expected:** {what should happen}
- **Actual:** {what happens instead}
## Context
- Discovered during: {session context}
- Related to: {PR, epic, or story if applicable}
- Severity: {high/medium/low}
Feature / Tech Debt / Task:
## Description
{What and why, in one paragraph}
## Context
- Related to: {epic, design doc, or story}
- Priority: {high/medium/low}
- Blocked by: {dependencies, if any}
Present the draft. Show the user the title + body before creating.
Create the issue. Use gh issue create --title "..." --body "..." with appropriate labels if the repo has them.
Report back. Show the issue URL and number. If this is related to an active epic, suggest adding it to the NEXT.md tech debt section.
| Type | Suggested label |
|---|---|
| Bug | bug |
| Feature | enhancement |
| Tech debt | tech-debt |
| Task | — |
gh issue list --search "...")