Create structured GitHub issues with sub-tasks and proper formatting. Use when organizing development work into trackable issues, breaking down features into parent/child issues, converting discussions into tracked work, or creating issues from conversation context.
Creates structured GitHub issues with sub-tasks from conversation context.
npx claudepluginhub linehaul-ai/linehaulai-claude-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
README.mdexamples.mdThis Skill helps you create well-structured GitHub issues directly from conversation context. It automatically organizes complex work into parent issues with sub-tasks, ensuring nothing gets lost in discussion.
Use this when you want to:
When you ask to create GitHub issues, I'll:
"Create GitHub issues for the carrier onboarding feature we just discussed"
"Create a parent issue for the new billing workflow with sub-tasks for:
- POD receipt handling
- Invoice ready flag logic
- Payment tracking"
"Create a parent issue for the load status bugs with individual sub-tasks for each problem"
"Create GitHub issues for the remaining work we discussed"
When you request issue creation, I'll delegate to the gh-issue-creator agent, which has access to:
gh) for issue creationThe agent will create issues that match your discussion and provide you with direct links to review them in GitHub.
This Skill works seamlessly with:
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.