Automate development task intake and execution from file paths, descriptions, or Git issues.
npx skills add https://github.com/kevinslin/skills --skill dev-do
Please help me install this Agent Skill. Skill: dev.do Source: https://github.com/kevinslin/skills/tree/main/active/dev.do Command: npx skills add https://github.com/kevinslin/skills --skill dev-do
End-to-end development task intake and execution, enabling teams to turn a user request (feature, bug, or refactor) into a delivered change by gathering context, asking clarifying questions if needed, and handing off to the dev.loop workflow to deliver the change.
Provide a dev task input (file path, pasted description, or git issue) and let dev.do orchestrate intake, clarification, and end-to-end execution.
High-intent search queries and answers about installing and using this skill.
Automating development task intake from a git issue involves classifying the request, gathering repository context, and orchestrating a dev.loop workflow to plan, implement, and verify changes. This Skill coordinates the entire process, creating a linked PR for traceability.
An end-to-end development workflow for LLM-driven execution takes a feature request, bug, or refactor and turns it into a delivered change by gathering context, asking clarifying questions, and running a structured loop to implement and verify the code.
Yes, you can use a pasted description to trigger automated code changes. The system accepts input from pasted descriptions, file paths, or Git issues, then automatically gathers relevant materials and runs the execution workflow to deliver the requested changes.
Yes, automated issue triage gathers repository context automatically. It collects relevant files, tests, and configurations during the intake phase, then asks concise clarifying questions if needed before proceeding with implementation.
The best way to handle development task intake and PR creation is to use an automated workflow that classifies the task, gathers context, and executes a dev.loop. This approach plans, implements, verifies, and cleans up changes while linking the final PR to the originating issue.
Yes, you need an LLM session to automate issue triage and execution. The workflow integrates with dev.llm-session and dev.research to gather context, plan implementations, and verify changes throughout the development loop.
WcofCollect and organize raw product discovery materials from multiple sources.
aidankinzettAutomate GitHub PR reviews via gh CLI with pending-review workflows.
CygnusfearCoordinate parallel oracle investigations and synthesize reports into a final document.
ZaxbyHubParse GitHub issue URLs into resolution specs with root cause hypotheses.
