finish-task

Verify code quality and merge feature branches into main.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lshtram/core_dev --skill finish-task-lshtram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-task
Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/finish-task
Command: npx skills add https://github.com/lshtram/core_dev --skill finish-task-lshtram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Concludes a task by verifying code quality and merging changes.

Core Features & Use Cases

  • Pre-merge verification: runs lint and tests to ensure changes are safe.
  • Safe merging: uses a non-fast-forward merge and cleans up worktrees and branches after successful merge.
  • Synchronization: updates local main with origin/main to avoid drift.
  • Cleanup: removes temporary worktrees and task branches to keep repository tidy.

Quick Start

Run this skill after completing a feature to verify code quality and perform a safe merge into main.

Frequently Asked Questions about finish-task

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

FAQPage Schema
How do I safely merge a feature branch into main after running tests?

A safe code merge requires verifying code quality by running lint and tests, synchronizing local main with origin/main, using a non-fast-forward merge, and cleaning up temporary worktrees and task branches.

What is the best way to clean up git worktrees and task branches after merging?

Cleaning up after a merge involves removing temporary worktrees and task branches once the feature changes are successfully merged, keeping the git repository tidy and free of obsolete references.

Why do I need to update local main with origin/main before merging a feature branch?

Updating local main with origin/main before merging is required to avoid branch drift, ensuring the feature branch integrates into the most current repository state for a safe and synchronized merge.

Does this pre-merge verification process run lint and tests automatically?

Yes, the pre-merge verification process runs lint and tests to ensure changes are safe before merging, verifying code quality automatically as part of the end-to-end merge governance workflow.

Can I use a non-fast-forward merge to preserve commit history when finishing a task?

Yes, you can use a non-fast-forward merge to preserve commit history when finishing a task, as this approach safely concludes the feature branch integration after verifying code quality and tests.

When should I not use a non-fast-forward merge for my code changes?

You should not use a non-fast-forward merge if your workflow strictly requires a linear commit history, as this approach specifically preserves branch context during the end-to-end merge governance process.