Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From odd-pipeline
File a bug report or feature request for the odd-pipeline itself, with auto-gathered context from the current project and session. Use when the user says "/file-issue", "file a bug", "report an issue", "this is a pipeline problem", or encounters a pipeline defect during daily use.
npx claudepluginhub tonywu20/my-claude-marketplace --plugin odd-pipelineHow this skill is triggered — by the user, by Claude, or both
Slash command
/odd-pipeline:file-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gathers context from the current project and session to file a structured issue on the `TonyWu20/odd-pipeline` repository. Lowers friction for reporting pipeline defects encountered during daily use.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
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.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Gathers context from the current project and session to file a structured issue on the TonyWu20/odd-pipeline repository. Lowers friction for reporting pipeline defects encountered during daily use.
/file-issue
No arguments. The skill prompts the user for issue details interactively.
The pipeline uses pluggable agents. Determine which agent to use for context gathering:
--agent-griller=<agent-name>, use that agent. CLI args override everything.AGENT_CONFIG.md from the project root. If it exists, parse **griller:** <agent-name>. Apply if not already set by CLI args.griller defaults to general-purpose.griller.Throughout this skill, whenever a subagent is launched, use the resolved agent name.
Launch the griller subagent (resolved in Step 0) to collect relevant context:
Agent: {griller} (subagent, discardable context)
Task: Gather context for a pipeline issue report.
Collect the following:
Current pipeline state:
ls skills/*/SKILL.md 2>/dev/nullPipeline version:
git log --oneline -5Current project context (from the working directory where the issue was encountered):
pwd git remote -v 2>/dev/null git log --oneline -3 2>/dev/nullOutput the gathered context as structured data for the issue template.
Format the issue using the GitHub issue template:
---
title: "[pipeline]: <short description>"
---
## Description
{User's description of the problem or feature request}
## Context
- **Pipeline version**: {commit hash from git log}
- **Project**: {current project URL or path}
- **Session**: {what skills were being used when the issue occurred}
## Reproduction Steps
{User-provided or auto-detected steps}
## Expected vs Actual
- **Expected**: {what should happen}
- **Actual**: {what actually happened}
## Environment
- **Pipeline branch**: {current branch}
- **OS**: {auto-detected}
- **Claude Code version**: {if available}
## Relevant Artifacts
{Paths to relevant plan files, directions.json, execution reports, etc.}
Present the formatted issue to the user for review and editing:
"Here's the draft issue for
TonyWu20/odd-pipeline:
{ISSUE_BODY}
Please review and edit the description above, then confirm to file the issue. Type 'confirm' to file, or provide changes."
Once the user confirms, file the issue:
gh issue create --repo TonyWu20/odd-pipeline --title "<title>" --body "<body>"
Report the resulting issue URL to the user.
Will:
gh CLIWill not: