tmchow/implementation-wrapup
plugins/iterative-engineering/skills/implementation-wrapup/SKILL.md
Complete a feature branch with test verification and PR creation. Triggers: "finish up", "create a PR", "wrap up the feature". Also invoked by iterative:implementing after all tasks are complete.
$ install --global
skillsauthnpx skillsauth add tmchow/tmc-marketplace implementation-wrapupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:30 AM10.6s1 file scanned
SKILL.md
- name:
- implementation-wrapup
- description:
- Complete a feature branch with test verification and PR creation. Triggers: "finish up", "create a PR", "wrap up the feature". Also invoked by iterative:implementing after all tasks are complete.
Implementation Wrapup
Completes development with verification, optional review, and PR creation.
When to Use
- After
iterative:implementingskill completes all tasks - When you're ready to create a PR
- When you want to finish a feature branch
- Can be invoked standalone on any branch
Workflow
Phase 1: Final Verification
- Run full test suite. If tests fail, stop and report failures.
- Check for uncommitted changes — commit or stash.
Phase 2: Optional Code Review
When invoked from iterative:implementing, skip this phase — all code reviews are already complete.
When invoked standalone:
- Present an interactive choice to the user —
AskUserQuestion(Claude Code) orrequest_user_input(Codex): A) Full code review (recommended), B) Skip review. - If review: invoke
code-reviewskill (1+ rounds). - Continue when review complete or skipped.
Phase 3: Context Summary
- Determine base branch (main/master/develop).
- Check if in worktree.
- Report: N commits, files changed, branch info.
Phase 4: Present Options
Present an interactive choice to the user:
- A) Push + PR (recommended) — creates new PR, or shows existing if one exists
- B) Push only
- C) Keep branch, don't push
- D) Discard work (typed confirmation required)
Phase 5: Execute
Option A — Push + PR: Push branch with -u, run gh pr create. If PR exists, show existing PR URL. If no PR, create one following repo conventions. Return PR URL.
Option B — Push only: Push branch, report remote URL.
Option C — Keep: Report branch preserved locally.
Option D — Discard: Require typed confirmation ("discard [branch-name]"). Delete branch (and worktree if applicable).
Phase 6: Cleanup
- If in worktree and work done, offer removal.
- Switch to base branch if not in worktree.
Safeguards
- Never skip test verification - tests must pass before any option
- Never push with failing tests - stop and report failures
- Never discard without typed confirmation - require exact branch name
- git push prompts user - not pre-approved, user confirms before pushing
PR Description
When creating a PR:
- Follow repo conventions from AGENTS.md/CLAUDE.md
- If no conventions: use conventional commits style
- Generate description from commit messages
- Keep title succinct and descriptive
Output Format
## Implementation Wrapup
### Verification
- Tests: PASS (N tests)
- Uncommitted changes: None / Committed
### Code Review
- Status: Completed / Skipped
- Issues addressed: N
### Summary
- Branch: feature/my-feature
- Base: main
- Commits: N
- Files changed: M
### Options
A) Push + Create PR (recommended)
B) Push only
C) Keep branch locally
D) Discard work
What would you like to do?
After Completion
Returns:
- PR URL (if created)
- Branch status
- Cleanup status (worktree removed if applicable)
Related Skills
tmchow/iterative:tech-planning
testing
VerifiedTrustedCommunity
Turn requirements into a structured implementation plan with subtasks, dependencies, file paths, and test scenarios. Triggers: "create a plan", "tech planning", "write a tech plan", or has requirements ready to formalize.
21SKILL.mdUpdated Apr 17, 2026
tmchow/iterative:research
data-ai
VerifiedTrustedCommunity
Investigate open questions through parallel research — prior art, constraints, competitive analysis. Triggers: "research this", "investigate questions", "resolve open questions", "look into this", or when a PRD has unresolved questions.
21SKILL.mdUpdated Apr 17, 2026
tmchow/plan-review
development
VerifiedTrustedCommunity
Review PRDs, brainstorm docs, tech plans, design docs, specs, or any planning document for issues. This skill should be used whenever the user wants feedback, critique, or a quality check on an existing planning or requirements document — even if they don't use the word "review." Common triggers include: "review the plan", "check the PRD", "critique my tech plan", "what's wrong with this plan", "poke holes in the requirements", "is this plan solid", "take a look at this spec", "give feedback on the brainstorm", or pointing to a doc file and asking if anything is off. Also triggers after writing a PRD or tech plan (to review what was just created), or when invoked by brainstorming or tech-planning skills. Do NOT trigger for code review (PRs, diffs, source files), writing/creating new plans, debugging, or reviewing non-planning documents (READMEs, CLAUDE.md, test coverage).
21SKILL.mdUpdated Apr 17, 2026
tmchow/iterative:implementing
development
VerifiedTrustedCommunity
Execute a tech plan with dependency-aware batching, TDD, code review, and PR creation. Triggers: "implement the plan", "start building", "start implementing", "execute the plan".
21SKILL.mdUpdated Apr 17, 2026