finish

Execute tests, self-review code, run validation checks, and confirm commits.

1|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill finish-hypejunction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/finish
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill finish-hypejunction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of concluding a work session by ensuring code quality, completeness, and proper commit hygiene, preventing common errors and saving time on manual checks.

Core Features & Use Cases

  • End-to-End Workflow: Guides you through testing, self-review, validation, and committing changes.
  • Quality Assurance: Enforces constraints like passing tests, no any types, and no secrets before committing.
  • Use Case: After implementing a new feature, you can run /finish to automatically run all necessary checks, fix minor issues, and prepare a clean commit, ensuring your work is production-ready before you sign off for the day.

Quick Start

Use the finish skill to complete your current work session by running tests, reviewing code, validating changes, and committing.

Frequently Asked Questions about finish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit validation and testing before ending a coding session?

Automated end-of-session validation runs tests, typechecks, and linting to ensure code quality before creating a git commit. It systematically performs self-reviews for security and code completeness, enforcing constraints like passing tests and no `any` types to guarantee a clean commit.

What is the best way to enforce code review and test coverage checks before a git commit?

Code review and test coverage checks are enforced by systematically executing validation workflows and security self-reviews prior to committing. This process blocks commits if constraints are unmet, such as failing tests or detecting hardcoded secrets, ensuring production readiness.

Does automated commit workflow validation check for security issues like exposed secrets?

Automated commit workflow validation includes self-reviews specifically designed to detect security issues like exposed secrets. It enforces strict constraints on sensitive data, type safety, and test coverage, preventing compromised code from being committed to the repository.

Can I use an end-of-session workflow to fix minor code issues and prepare a final commit?

End-of-session workflows can fix minor code issues during the validation phase before preparing a confirmed git commit. By running tests, typechecks, and linting, the workflow resolves detected problems and outputs a structured session summary with clear next steps.

Why should I use an automated workflow for git commits instead of manual testing and review?

Automated workflows prevent common manual errors by systematically enforcing code quality, type safety, and test coverage constraints before committing. They save time on manual checks and provide structured output for session summaries, ensuring consistent commit hygiene and production-ready code.

What are the limitations of using automated validation constraints for git commits?

Automated validation constraints strictly block commits when tests fail, `any` types are detected, or secrets are present. This means developers cannot bypass these quality checks, which may temporarily stall a commit if minor issues require manual intervention to resolve.