Individual skill
wrap-up-branch
Finish a feature branch: add missing tests, review and fix the code, align docs, then merge only after explicit confirmation.
plugins/reidemeister94/development-skills/skills/wrap-up-branch/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,422 bytesagents/openai.yamlasset · 170 bytes
Read excerpt
# Wrap up branch
Finish the current feature branch so it can land safely.
Invoking the skill authorizes in-scope edits, their commits on the feature branch, and merging the target into the feature branch.
Merging into the target and pushing wait for the final question.
Run the steps in order. Stop on a failed gate.
Each step that changes files ends with `development-skills:commit` and the matching Conventional Commit type.
## 1. Resolve scope
- The feature branch is the current `HEAD`. Stop on a detached `HEAD` or when `HEAD` is already the target.
- The target is `$ARGUMENTS`. Without it, inspect `dev`, `develop`, and `development`; otherwise use the default branch.
- Name `main` or `master` as protected in the final question.
- A dirty working tree needs one decision: commit the listed paths or stop. Never stash without permission.