dev-workflows

Routes development requests to bug-fix, code-review, documentation, performance, security, or test workflows.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ntd237/draft_toolkits_20042026 --skill dev-workflows-ntd237
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-workflows
Source: https://github.com/ntd237/draft_toolkits_20042026/tree/main/.agents/skills/dev-workflows
Command: npx skills add https://github.com/ntd237/draft_toolkits_20042026 --skill dev-workflows-ntd237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development requests often mix multiple intents—fixing a bug, reviewing the change, writing tests, and updating docs—and handling them ad hoc leads to skipped steps, wrong ordering, and incomplete checklists. This Skill classifies each request by intent and runs the correct workflow checklists in a safe dependency order. ## Core Features & Use Cases - Intent-Based Routing: Keyword routing table maps requests to one of six workflows: bug-fix, code-review, documentation, performance-optimization, security-review, or tests. - Dependency-Ordered Execution: Multi-intent requests run in a fixed order—fix bugs and vulnerabilities first, then optimize, test, review, and document last. - Structured Checklists: Each workflow has a concrete checklist, such as root cause analysis for bugs, six security review categories, and test coverage across happy paths, edge cases, and integration points. - Use Case: A user asks to "fix the login crash, then review and test the fix." The Skill runs bug-fix first with root cause analysis, generates regression tests, then performs a five-area code review, ending with a summary of files touched. ## Quick Start Ask the assistant to fix a bug, review code, generate documentation, optimize performance, run a security review, or write test cases for specific files in your project.

Frequently Asked Questions about dev-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route a coding request to the right development workflow?▼

Match the request against the routing table: bug or error keywords trigger bug-fix, review triggers code-review, docs trigger documentation, performance triggers optimization, security triggers security-review, and test triggers the tests workflow. Ambiguous intent should be clarified with the user before executing.

How to handle a request that asks for a bug fix, tests, and code review together?▼

Run the workflows in dependency order: bug-fix first, then tests for the change, then code-review of the final diff, and documentation last. Label each workflow's output with its own header and end with a summary section.

What does the security review checklist cover?▼

The security review covers six categories: input validation, authentication and authorization, data exposure and PII, injection vulnerabilities such as SQL and XSS, cryptographic implementation, and dependencies with known CVEs. Findings are ranked by severity with specific recommendations.

Can this workflow review code without reading the files first?▼

No. The Skill explicitly forbids running any workflow without first reading the relevant files. Blind review or analysis is prohibited, and every optimization suggestion must include a specific mechanism and expected impact.

What test cases does the tests workflow generate?▼

It generates happy path scenarios, edge cases and boundary conditions, error handling tests, integration tests with mocks or stubs, performance considerations, and security edge cases. Tests follow the project's existing testing framework conventions with setup and teardown as needed.