Drive Implementation Workflow FAQs

Name: Drive Implementation Workflow
Author: qmu

Question 1

Does this skill automatically commit my changes?

Accepted Answer

No, the Drive Workflow skill specifically prohibits automated commits. It implements the changes and prepares a summary, leaving the final approval and commit process to the parent /drive command.

Question 2

Can I use this skill to archive tickets?

Accepted Answer

No, ticket archiving and status updates are handled by the core /drive command after the implementation workflow has successfully returned its summary.

Question 3

Does it verify code quality during implementation?

Accepted Answer

Yes, the workflow requires running project-specific type checks and fixing errors or test failures before the implementation is considered complete.

Question 4

How does it handle git patches?

Accepted Answer

The skill scans tickets for a Patches section, writes them to temporary files, and validates them using 'git apply --check' before implementation to ensure a clean application process.

Question 5

Is this skill safe for team environments?

Accepted Answer

Yes. It includes strict prohibited operations such as 'git clean' and 'git reset --hard' to ensure that uncommitted work from other team members is never accidentally discarded.

Drive Implementation Workflow

主要功能

使用场景

Drive Implementation Workflow

主要功能

使用场景