agentsclimarketplace

Finishing a development branch

Skill dariovr1/sixth-sense/skills/finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup.From its SKILL.md

Install
npx -y skills add dariovr1/sixth-sense --skill finishing-a-development-branch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, as published. Nobody here has run it

Finishing a Development Branch

Core Principle

Verify tests → Present options → Execute choice → Clean up.

The Process

Step 1: Verify Tests

Before presenting any options, verify that all tests pass:

  • Java: ./gradlew test
  • Node.js/Angular: npm test / ng test
  • Apply verification-before-completion — evidence before claims.

Step 2: Present Options

Once tests are verified, present the following structured options to the user:

  1. Merge to main: Direct merge for simple changes.
  2. Create PR: Open a pull request for team review.
  3. Keep branch: Preserve the current branch and worktree for later work.
  4. Clean up: Remove the branch and clean up the worktree.

Step 3: Execute Choice

Systematically handle the workflow chosen by the user, ensuring all necessary git operations are completed.

Create PR: the description is not a diff summary — a reviewer can already see the diff. Include: what this changes and why (one or two sentences), a link/reference to the spec or issue it implements if one exists, and the verification evidence (test suite result, not "tests pass" unsubstantiated — same evidence-before-claims bar as verification-before-completion). Skip a section entirely rather than filling it with "N/A" or restating the title.

Step 4: Cleanup Artifacts

After executing the chosen option, ask if the user wants to remove any artifacts created during the session (e.g., plans, specs, or .bak files).

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.