task-completer by camoa/claude-skills
npx skills add https://github.com/camoa/claude-skills --skill task-completer完成任务并更新项目记忆。
在完成任何任务前加载:
| 参考 | 强制执行 |
|---|---|
references/quality-gates.md | 关卡 2, 3, 4 (必须全部通过) |
| 开发指南: https://camoa.github.io/dev-guides/drupal/security/ | 关卡 4 安全审查 |
当检测到以下情况时激活:
/drupal-dev-framework:complete 命令在所有关卡通过之前,任务无法完成:
| 关卡 | 检查项 |
|---|
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 是否阻塞? |
|---|
| 关卡 1 | 代码标准 (调用 code-pattern-checker) | 是 |
| 关卡 2 | 测试通过 (用户确认) | 是 |
| 关卡 3 | 架构合规性 | 是 |
| 关卡 4 | 安全审查 | 是 |
对任务文件使用 Read 操作:{project_path}/implementation_process/in_progress/{task}.md
检查每个验收标准。询问用户:
{task_name} 完成检查清单:
验收标准:
- [ ] {criterion 1} - 完成了吗?
- [ ] {criterion 2} - 完成了吗?
- [ ] {criterion 3} - 完成了吗?
确认所有验收标准都已满足 (是/否):
如果为"否",则识别剩余工作并继续处理。
所有关卡必须在完成前通过:
对修改过的文件调用 code-pattern-checker 技能。
\Drupal::service()请用户确认:
测试验证 (用户必须运行):
ddev phpunit {test_path}
- [ ] 所有现有测试都通过了吗?
- [ ] 新代码有测试覆盖吗?
- [ ] 没有未经记录原因而跳过的测试吗?
确认测试通过 (是/否):
对照 architecture/main.md 检查:
https://camoa.github.io/dev-guides/drupal/security/ 以获取详细安全指南如果任何阻塞关卡失败: 任务完成被阻止。先修复问题。
使用 Edit 在任务文件中添加完成部分:
---
## 完成情况
**完成日期:** {YYYY-MM-DD}
**最终状态:** 完成
### 摘要
{对所实现内容的简要描述}
### 更改的文件
| 文件 | 操作 |
|------|--------|
| src/... | 已创建 |
| tests/... | 已创建 |
| *.services.yml | 已修改 |
### 测试结果
- 单元测试:{count} 通过
- 内核测试:{count} 通过
- 总计:全部通过
### 备注
{任何实现说明、偏差或做出的决策}
使用 Bash 移动任务:
mv "{project_path}/implementation_process/in_progress/{task}.md" "{project_path}/implementation_process/completed/{task}.md"
使用 Edit 更新:
## 进度
### 已完成的任务
| 任务 | 完成日期 | 备注 |
|------|-----------|-------|
| {task_name} | {date} | {一行摘要} |
## 当前重点
{更新为下一个任务或"准备下一个组件"}
使用 Glob 查找剩余任务:
{project_path}/implementation_process/in_progress/*.md
分析依赖关系和优先级。呈现:
任务完成:{task_name}
下一个任务选项:
1. {next_task} - {原因:依赖关系已解除 / 优先级}
2. {alternative} - {原因}
3. 没有更多任务 - 组件已完成
下一个选择哪个任务? (1/2/3 或其他):
如果这是组件的最后一个任务,建议:
组件 {name} 似乎已完成。
运行最终验证吗?
- superpowers:verification-before-completion
- 完整测试套件
- 集成测试
继续吗? (是/否)
停止并等待用户:
每周安装数
1
仓库
GitHub 星标数
17
首次出现
今天
安全审计
安装于
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
Finalize tasks and update project memory.
Load before completing any task:
| Reference | Enforces |
|---|---|
references/quality-gates.md | Gates 2, 3, 4 (must ALL pass) |
| dev-guides: https://camoa.github.io/dev-guides/drupal/security/ | Gate 4 security review |
Activate when you detect:
/drupal-dev-framework:complete commandTask CANNOT be completed until ALL gates pass:
| Gate | Check | Blocking? |
|---|---|---|
| Gate 1 | Code standards (invoke code-pattern-checker) | YES |
| Gate 2 | Tests pass (user confirms) | YES |
| Gate 3 | Architecture compliance | YES |
| Gate 4 | Security review | YES |
Use Read on the task file: {project_path}/implementation_process/in_progress/{task}.md
Check each acceptance criterion. Ask user:
Completion checklist for {task_name}:
Acceptance Criteria:
- [ ] {criterion 1} - Is this done?
- [ ] {criterion 2} - Is this done?
- [ ] {criterion 3} - Is this done?
Confirm all acceptance criteria are met (yes/no):
If NO, identify what's remaining and continue working.
ALL gates must pass before completion:
Invoke code-pattern-checker skill on modified files.
\Drupal::service() in new codeAsk user to confirm:
Tests verification (user must run):
ddev phpunit {test_path}
- [ ] All existing tests pass?
- [ ] New code has test coverage?
- [ ] No skipped tests without documented reason?
Confirm tests pass (yes/no):
Check against architecture/main.md:
https://camoa.github.io/dev-guides/drupal/security/ for detailed security guidanceIf ANY blocking gate fails: Task completion is BLOCKED. Fix issues first.
Use Edit to add completion section to the task file:
---
## Completion
**Completed:** {YYYY-MM-DD}
**Final Status:** Complete
### Summary
{Brief description of what was implemented}
### Files Changed
| File | Action |
|------|--------|
| src/... | Created |
| tests/... | Created |
| *.services.yml | Modified |
### Test Results
- Unit tests: {count} passing
- Kernel tests: {count} passing
- Total: All passing
### Notes
{Any implementation notes, deviations, or decisions made}
Use Bash to move the task:
mv "{project_path}/implementation_process/in_progress/{task}.md" "{project_path}/implementation_process/completed/{task}.md"
Use Edit to update:
## Progress
### Completed Tasks
| Task | Completed | Notes |
|------|-----------|-------|
| {task_name} | {date} | {one-line summary} |
## Current Focus
{Update to next task or "Ready for next component"}
Use Glob to find remaining tasks:
{project_path}/implementation_process/in_progress/*.md
Analyze dependencies and priorities. Present:
Task complete: {task_name}
Next task options:
1. {next_task} - {reason: dependency unblocked / priority}
2. {alternative} - {reason}
3. No more tasks - component complete
Which task next? (1/2/3 or other):
If this was the last task for a component, suggest:
Component {name} appears complete.
Run final validation?
- superpowers:verification-before-completion
- Full test suite
- Integration tests
Proceed? (yes/no)
STOP and wait for user:
Weekly Installs
1
Repository
GitHub Stars
17
First Seen
Today
Security Audits
Gen Agent Trust HubPassSocketFailSnykWarn
Installed on
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
开源项目教练指南 - 诊断问题、制定行动计划、优化开源项目运营
31,600 周安装