Read ticket content, apply patches, and implement changes with verification.
npx skills add https://github.com/qmu/workaholic --skill drive-workflow
Please help me install this Agent Skill. Skill: drive-workflow Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/drive-workflow Command: npx skills add https://github.com/qmu/workaholic --skill drive-workflow
This Skill defines a deterministic workflow to implement a single ticket end-to-end within the drive command, ensuring changes are applied correctly and prepared for review.
Use the drive-workflow skill to implement a single ticket during a /drive session by pointing to the ticket file the command will read, patch, and apply changes, then report back for approval.
High-intent search queries and answers about installing and using this skill.
Ticket-driven code implementation automates reading a ticket file, applying patches, and executing changes. This workflow processes tickets step-by-step within a drive session to deliver verified code modifications ready for review.
To apply patches and validate changes, the workflow reads the ticket content, executes patch application, and runs type checks. It ensures changes follow repository patterns and returns a concise summary for approval without committing.
Yes, ticket-driven workflow requires a clean git working tree. It also requires a ticket file in the repository and standard tooling including git, patch validation, and type checks to verify changes before reporting.
Yes, you can process multiple tickets one by one during a drive session. The workflow implements each ticket sequentially, applying patches and verifying changes step-by-step to deliver a final summary for approval.
Ticket-driven code implementation stops before committing because it prepares changes for review. It runs validations and type checks, then returns a concise summary for approval, ensuring modifications are verified without automatically altering the git history.
Setting up for automated ticket patch application requires a ticket file in the repository, a clean working tree, and standard tooling. You need git, patch validation, and type checks configured to verify changes before reporting.
agentclashValidate git commit hygiene and working tree status post-commit.
TakSungTrack Git repository changes and summarize status, commits, and diffs.
CsHengRun Ruff, Mypy, and Pytest checks on Python code.
ZegocoverAutomate JIRA bug resolution from diagnosis through PR creation.
