From devflow
Creates issues with codebase analysis. Use this when the user wants to create a new issue, file a bug, or add a feature request to Jira, GitLab, or GitHub.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin codingthefuturewithai-claude-code-primitivesThis skill is limited to using the following tools:
I'll create a detailed issue (Feature/Bug) with codebase analysis and research.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
I'll create a detailed issue (Feature/Bug) with codebase analysis and research.
Request: $ARGUMENTS
Reference docs: Load ../references/issue-standards/core-standards.md (always), then the type-specific file based on issue type selected in Step 1:
../references/issue-standards/feature-standards.md + ../references/issue-standards/FEATURE-EXAMPLE.md../references/issue-standards/bug-standards.md + ../references/issue-standards/BUG-EXAMPLE.md../references/issue-standards/other-types.mdUse the build-ops skill to:
devflow-config.mdThe build-ops skill handles all backend-specific operations (Jira, GitLab, GitHub)
and enforces parameter validation. See skills/build-ops/SKILL.md.
🚨 CRITICAL: Ask ONE question at a time. Wait for user response before next question.
🚨 CRITICAL: MCP handles authentication - NEVER ask for URL/cloudId/credentials!
Project Selection:
Use the build-ops skill's project discovery to list available projects.
Ask ONLY: "Which project?" [Display projects from backend]
WAIT. Store selected project identifier.
Issue Type:
Ask ONLY: "What type of issue?"
Options:
WAIT.
[Map to issue types]:
[For Jira: Call mcp__atlassian__getJiraProjectIssueTypesMetadata to verify type exists]
Title:
[Suggest title based on description]
Ask ONLY: "Use this title: '[suggested]' or provide your own?"
WAIT. Store title.
Priority:
Ask ONLY: "Priority? (High/Medium/Low)"
WAIT. Default Medium if unclear.
[Use Grep/Glob/Read to find]:
Present findings with file paths.
[Based on user's description and codebase analysis from Step 2]:
If feature requires library/tool NOT in codebase:
Say: "This feature needs [library X]. I don't see it in the project. Research options with Context7?"
Ask ONLY: "Yes or No?"
WAIT.
If Yes:
mcp__context7__resolve-library-idmcp__context7__get-library-docsSummarize strategic insights (which library, why, trade-offs) - NOT API docs.
If feature uses existing libraries:
Draft the issue following the standards from the loaded reference files:
Core principle: WHAT (outcomes, capabilities), not HOW (implementation). See core-standards.md.
[Extract from description + analysis]
Say: "Suggested: [label1], [label2], [label3]"
Ask ONLY: "Use these or edit/add?"
WAIT. Store labels.
Show complete preview:
Ask ONLY: "Create this issue?"
Options: "Yes / Edit / Cancel"
⏸️ WAIT for explicit "Yes"
[Only if approved]
Use the build-ops skill to create the issue in the configured backend with:
The build-ops skill handles all backend-specific creation logic and enforces
parameter validation. See skills/build-ops/SKILL.md.
Return: Issue key/number, URL, suggested branch name.
Never:
Always: