Vibe Coding
Guide a nontechnical builder through small observable iterations; inspect generated changes and verify a real task.
Close implementation with verification, reviewable changes, and clearly stated integration options.
---
name: knoveya-finishing-a-development-branch
description: "Close implementation with verification, reviewable changes, and clearly stated integration options. Use for matching engineering work."
---
# Finishing a Development Branch
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Close implementation with verification, reviewable changes, and clearly stated integration options.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
No commit, push, or merge happens without the required authorization.
## Example task
Offer a conventional commit suggestion after tests pass.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-finishing-a-development-branch as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-finishing-a-development-branch/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Offer a conventional commit suggestion after tests pass.
No commit, push, or merge happens without the required authorization.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.