finalize
From the author
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
Install
npx skills add tobihagemann/turbo --skill finalize -a claude-code
Installs to .claude/skills/finalize/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 86
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- quick-finalizetobihagemann/turboClose out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the full review", or "ship this without the deep pass".Testing★ 417
- implementtobihagemann/turboLoad code-style and task-specific skills, make the change described by the current context, then run post-implementation QA. Use for ad-hoc changes when no plan file or improvements backlog governs the work, and when the user asks to "just implement", "implement directly", "implement without a plan", or "apply the change".Testing★ 417
- resolve-findingstobihagemann/turboImplement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Use after /evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "apply evaluated findings", or "dispatch findings to implementation".Testing★ 417
- review-testingposit-dev/skillsReview test code for quality, design, and completeness after implementing a feature or fixing a bug. Use when the user asks to "review my tests", "check my test quality", "are these tests good enough", "review testing", or after completing a feature implementation that includes tests. Also use when tests feel brittle, flaky, or superficial. Cross-references production code to find coverage gaps.Testing★ 545
- review-implementingmhattingpete/claude-skills-marketplaceProcess and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.Engineering★ 687
- verification-before-completionGanyuanRan/AegisUse when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.Engineering★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in