amElnagdy/delegate-skills / skills/qoder-delegate
qoder-delegate
VerifiedDelegate a coding task to the Qoder CLI (`qodercli`) as a background implementer, then review its diff and land it yourself. Use this whenever the user asks to have Qoder implement, fix, refactor, or run a queue of coding tasks while the orchestrator remains the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants code written directly without delegation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/dispatch-and-poll.md | markdown | 5.6 KB |
| references/multi-task-queues.md | markdown | 1.5 KB |
| references/review-and-land.md | markdown | 2.5 KB |
| references/writing-the-brief.md | markdown | 3.4 KB |
| scripts/relay.mjs | script | 25.1 KB |
references/review-and-land.md
View on GitHub# Review and land
Qoder did the typing; the orchestrator owns the judgment. Verify reality, not the self-report.
## Review changed tests first
- Treat unbriefed test edits as contract changes.
- Treat skipped, disabled, or commented tests as failures.
- Treat loosened assertions as weakened gates.
## Re-run the gates
`finalMessage` contains Qoder's claims. Run the repository's actual test, lint, typecheck, and build
commands yourself. For specialized changes:
- Round-trip migrations and schemas.
- Search for dangling references after removals and renames.
- Exercise stateful behavior, not only compilation.
## Compare the diff to the brief
Start with `touchedFiles`, then read the full diff for:
- **Scope creep** - excluded changes.
- **Scope shortfall** - missing behavior or cleanup.
- **Quiet decisions** - defensible but unasked choices requiring review.
`touchedFiles` is final tree state, not attribution. Start clean when possible and inspect every
`--add-dir` workspace separately.
## Implementer sweep
Look for hardcoded success data, swallowed errors, nonexistent dependencies or APIs, dead helpers,
duplicate patterns, tests that assert internals, speculative options, and guards that hide missing
trust-boundary validation. Run relevant guard skills if installed.
## Rework with a delta brief
Continue the same Qoder session with only the correction:
```bash
echo "Keep the fix, replace the mocked DB assertion with the real migrated fixture, remove the unused import, and rerun the stated gates." |
node "<skill-dir>/scripts/relay.mjs" --resume-last --cd /path/to/repo
```
Use `--resume <id>` for the specific `sessionId` in `result.json`. Rework receives the same independent
gate and diff review.
## Commit boundary
When the gates pass and the diff holds, **the orchestrator commits**. Qoder must never run `git add` or
`git commit` for this workflow.
Until then, the working tree is the authoritative copy of the implementer's work. Before any cleanup
or branch switch, inspect `git status`, `git diff`, `git diff --cached`, and every untracked file.
Staged and untracked work is invisible to a plain `git diff`; preserve it until the review decides
what to keep.
## Surface, do not absorb
- Report Qoder's design decisions and defensible deviations.
- Note non-blocking issues you did not block on.
- Stop and ask when correct completion requires expanding the brief.
For queues, keep these notes in the progress file described in
[multi-task-queues.md](multi-task-queues.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |