wrap-up-branch skillA
wrap-up-branch is agent-read markdown (skill) from reidemeister94/development-skills: Finish a feature branch: add missing tests, review and fix the code, align docs, then merge only after explicit confirmation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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. - Fetch `origin`, then use `git diff <merge-base>...HEAD` as the scope. Keep temporary review files outside the repository. - Run the project's checks as a baseline. Stop if the branch is already red. - State the target and merge-base before changing the branch. ## 2. Tests Invoke `development-skills:create-test` for the branch scope. …
Read the whole file at its exact version.
How to install
mdr add reidemeister94/development-skills/wrap-up-branch@git:20260919.a9f7da5mdr add reidemeister94/development-skills/wrap-up-branch@sha256:afa5d77fb6744053Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_dnr4ntz4kg5hjiuz)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3422 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
reidemeister94/development-skills · 12 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dnr4ntz4kg5hjiuz GET https://markdownregistry.com/api/v1/resolve?ref=reidemeister94/development-skills/wrap-up-branch GET https://markdownregistry.com/api/v1/blob/afa5d77fb6744053dfaaa726efc0c234bc5333d51f33dce1676b0448354e2ed6
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.