npx claudepluginhub dylanliiii/shipyard --plugin VengineerThis skill is limited to using the following tools:
**Purpose**: Report bugs or request features for the Vengineer plugin. This command gathers structured information and creates a GitHub issue in the VitaDynamics/vita-cc-market repository.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Purpose: Report bugs or request features for the Vengineer plugin. This command gathers structured information and creates a GitHub issue in the VitaDynamics/vita-cc-market repository.
Before proceeding, verify that the user has authenticated with the GitHub CLI:
# Check if gh is authenticated
gh auth status
If the user is NOT authenticated:
gh auth login firstIf authenticated, proceed to Step 1.
First, ask the user what type of report they want to submit:
Question: Report Type
Proceed to Step 2 with the appropriate context.
Use the AskUserQuestion tool to collect the following information:
Question 1: Bug Category
Question 2: Specific Component
Question 3: What Happened (Actual Behavior)
Question 4: What Should Have Happened (Expected Behavior)
Question 5: Steps to Reproduce
Question 6: Error Messages
Automatically gather:
# Get plugin version
cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "Vengineer" | head -10 || echo "Plugin info not found"
# Get Claude Code version
claude --version 2>/dev/null || echo "Claude CLI version unknown"
# Get OS info
uname -a
Create a well-structured report based on the request type:
For Bug Reports:
## Bug Description
**Component:** [Type] - [Name]
**Summary:** [Brief description from argument or collected info]
## Environment
- **Plugin Version:** [from installed_plugins.json]
- **Claude Code Version:** [from claude --version]
- **OS:** [from uname]
## What Happened
[Actual behavior description]
## Expected Behavior
[Expected behavior description]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Error Messages
[Any error output]
## Additional Context
[Any other relevant information]
---
*Reported via `/report-bug` command*
For Feature Requests:
## Feature Request
**Component:** [Type] - [Name]
**Summary:** [Brief description]
## Proposed Feature
[Describe the feature you want to see implemented]
## Motivation
[Explain why this feature would be useful]
## Proposed Solution
[If you have ideas on how this could be implemented, describe them here]
## Alternatives Considered
[Any alternative approaches you've considered]
## Additional Context
[Any other relevant information]
---
*Reported via `/report-bug` command*
After formatting the report, ask the user:
Question: Action
gh issue createIf user selects "Create GitHub Issue":
# Create issue with appropriate labels
gh issue create --title "[Report Type]: [Brief description]" --body "$REPORT_CONTENT" --label "bug" --label "plugin" --repo "VitaDynamics/vita-cc-market"
Provide the issue URL to the user.