coding-agent-delivery
paean-ai/deeptide/skills/coding-agent-delivery/SKILL.md
Use this skill when a local coding agent must turn implementation work into a reviewable engineering artifact: plan, diff summary, verification, risks, reviewer focus, and PR description. Make agent work easy to inspect and merge. The final output should explain what changed, why it changed, how it was verified, and what risk remains. Use this order: For small changes, compress this into a concise paragraph plus verification. For substantial work, use a structured artifact or PR body. Choose checks based…
What's in it
- Coding Agent Delivery
- Goal
- Delivery Shape
- PR Summary Template
- Engineering Standards
- Verification Matrix
- Handoff Notes
- Common Mistakes
# Coding Agent Delivery Use this skill when a local coding agent must turn implementation work into a reviewable engineering artifact: plan, diff summary, verification, risks, reviewer focus, and PR description. ## Goal Make agent work easy to inspect and merge. The final output should explain what changed, why it changed, how it was verified, and what risk remains. ## Delivery Shape Use this order: 1. Objective 2. Implementation summary 3. Public interfaces or behavior changes 4. Verification performed 5. Risks and rollback 6. Reviewer focus For small changes, compress this into a concise paragraph plus verification. For substantial work, use a structured artifact or PR body. ## PR Summary Template ```md ## Summary - Added ... - Updated ... - Preserved ... ## Verification - `npm test -- ...` - `npm run typecheck` - Manual: ... ## Risks - ... ## Reviewer Focus - ... ``` ## Engineering Standards - Read the existing code before editing. - Keep changes scoped to the request. - Prefer existing patterns and helpers. - Avoid unrelated refactors. - Do not revert user changes. - Make tests proportional to risk. - Surface failed or skipped verification honestly. ## Verification Matrix Choose checks based on blast radius: - Syntax: language-specific parser or `node --check`. - Types: typecheck, compiler, or build. - Behavior: focused unit/integration tests. - UI: desktop/mobile screenshots, layout inspection, no console errors. - Git: `git diff --check`, `git status`, branch sync. - Security: secret scan and public-repo review. ## Handoff Notes Good handoff notes answer: - What was requested? - What files or subsystems changed? - What should the reviewer inspect first? - What did the agent verify? - What remains uncertain? - How can the change be rolled back? ## Common Mistakes - Reporting tests as passing when they were not run. - Listing every edited symbol instead of behavior-level changes. - Hiding residual risk. - Mixing unrelated cleanup into the same change. - Leaving a local server or long-running process active.
More agent context in paean-ai/deeptide
9 other files this repository gives its agents.
Skill
- casual-game-systemsskills/casual-game-systems/SKILL.md
- html-deck-templateskills/html-deck-template/SKILL.md
- pixel-art-codeskills/pixel-art-code/SKILL.md
- premium-visual-styleskills/premium-visual-style/SKILL.md
- publishskills/publish/SKILL.md
- remixskills/remix/SKILL.md
- research-brief-deliveryskills/research-brief-delivery/SKILL.md
- responsive-canvas-gameskills/responsive-canvas-game/SKILL.md
- roguelike-game-templateskills/roguelike-game-template/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

