dev-workflow
No SKILL.md available for this skill.
View on GitHubMore from hubvue/skills
dev-spec
Spec-driven development workflow skill for product requirement intake, engineering research, technical planning, task breakdown, implementation, testing, bugfix loop, and engineering review. Use when a user wants to run or continue a structured software delivery workflow with explicit specs, durable artifacts, and iterative implementation/testing loops.
3skills-workflow
Interactive skills workflow for chaining multiple skills where the output of step i becomes the input of step i-1. Use when you need to: (1) Chain multiple skills together in a specific order, (2) Pass outputs between skills as inputs, (3) Execute complex multi-step workflows with traceability, (4) Run skills in dry-run mode before execution, (5) Debug or audit multi-skill workflows
3release-skills
Release workflow for baoyu-skills plugin. Use when user says "release", "发布", "push", "推送", "new version", "新版本", "bump version", "更新版本", or wants to publish changes to remote. Analyzes changes since last tag, updates CHANGELOG (EN/CN), bumps marketplace.json version, commits, and creates version tag. MUST be used before any git push with uncommitted skill changes.
3api-generator
Autonomous Frontend Code Generation Agent specialized in project-aware API integration. Use when user provides backend API specs needing frontend request code, mock data to convert to request types and handlers, API endpoints to add with types mocks and tests, or new API integration following existing project conventions. Automatically detects TypeScript, request patterns, mock infrastructure, and test frameworks to generate artifact-gated code.
3skills-workflow-builder
Create a new dedicated workflow skill by reusing the existing skills-workflow (to collect/normalize a pipeline) and the existing skill-creator (to materialize the new skill). Use when you want a reusable workflow skill without re-entering skill order/templates each time.
3project-migration
Plan and drive safe old-to-new project or repository migrations with phase-based outputs, risk controls, and migration artifacts. Use when a user needs to: (1) audit an inherited or undocumented project before migration, (2) compare old and new repositories across tooling, architecture, routing, state, request, styling, CI/CD, or release flow, (3) produce migration deliverables such as audits, maps, diff matrices, plans, pilot scopes, adapter plans, risk lists, or verification checklists, (4) execute or update a specific migration phase such as intake, audit, map, diff, plan, pilot, execute, verify, or cleanup.
2