Agent Skills › a1stok/img2svg-animation › do-work

do-work

GitHub

提供从探索规划到代码提交的全流程实现工作流，涵盖数据库与前端特定TDD规范、类型检查、测试验证及Git操作，确保功能完整交付。

.agents/skills/do-work/SKILL.md a1stok/img2svg-animation

Trigger Scenarios

用户需要实现新功能用户需要修复Bug 需要进行端到端代码变更并验证

Install

npx skills add a1stok/img2svg-animation --skill do-work -g -y

More Options

Non-standard path

npx skills add https://github.com/a1stok/img2svg-animation/tree/master/.agents/skills/do-work -g -y

Use without installing

npx skills use a1stok/img2svg-animation@do-work

指定 Agent (Claude Code)

npx skills add a1stok/img2svg-animation --skill do-work -a claude-code -g -y

安装 repo 全部 skill

npx skills add a1stok/img2svg-animation --all -g -y

预览 repo 内 skill

npx skills add a1stok/img2svg-animation --list

SKILL.md

Frontmatter

{
    "name": "do-work",
    "description": "End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed."
}

Do Work

Complete implementation workflow from exploration to commit.

Workflow

Phase 1: Explore & Plan

Phase 2: Implement

If you're touching code that interacts with the database, follow the DB TDD workflow.

If you're touching frontend code with complex state (creating/modifying reducers, complex state transitions, non-trivial state management), follow the Frontend TDD workflow.

Phase 3: Feedback Loops & Verification

Run each check, fix issues, and re-run until clean. Do these sequentially:

Type checking: npm run typecheck
Tests: npm test

If a check fails, fix the issue and re-run that check before moving to the next one. Do not move on with failing checks.

Verify Acceptance Criteria: Review the original sub-issue body. Ensure all acceptance criteria are met.
- If the implementation is complex, consider invoking a subagent (e.g., research or self) or manually running the app to verify the end-to-end behavior matches what was promised.
- Update the sub-issue on GitHub to check off the completed acceptance criteria boxes (e.g., replace [ ] with [x]).

Phase 4: Commit & Close

One Commit per Sub-Issue: Once all tests pass and criteria are verified, commit your work to the active branch following the rules in docs/committing.md.
Close Sub-Issue: If you were working on a GitHub sub-issue, close it using the GitHub CLI (gh issue close <issue-number>) at the end of your implementation run.
Push Commits: Push your branch to remote. If you are working on master, simply push. If you are on an agent branch, you may merge it to master and push if the milestone is complete.
Draft PR (Optional): Only open a Pull Request if the user explicitly requested a code review or a PR. If just commits are enough, do not create a PR. If the final sub-issue of a PRD is completed, manually close the parent PRD.