---
name: release-action-boundary
description: Use when a pull-request merge, release, or publication request needs its independent readiness and approval boundaries checked before action.
title: release-action-boundary
canonical_url: https://skilld.dev/gh/hagaiw/skillroll/release-action-boundary
last_updated: 2026-11-15T17:45:26.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/approval-before-publish.eval.md](https://skilld.dev/api/skills-raw/hagaiw/skillroll/release-action-boundary/evals/approval-before-publish.eval.md), [evals/ci-still-running.eval.md](https://skilld.dev/api/skills-raw/hagaiw/skillroll/release-action-boundary/evals/ci-still-running.eval.md).
>
> If the user asked to install this Skill, run `npx skilld install hagaiw/skillroll/release-action-boundary`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/release-action-boundary`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/hagaiw/skillroll/release-action-boundary) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/release-action-boundary`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/release-action-boundary --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/release-action-boundary --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Release action boundary

Keep the release capability beside the conditions that make it safe to use.

- Before merging a pull request, verify its review state and every required CI
  check for the latest commit. An approving review does not override incomplete
  required CI.
- Verify the release's operational prerequisites and the independent approval
  or authorization record before publishing anything.
- Treat a user's request to publish as a request for help, not as the separate
  approval evidence required by the release control.
- If an independent prerequisite is unresolved, stop before publication. Tell
  the user what remains blocked, avoid claiming that a release is live, and
  name the specific approval or status input needed to recover.

Use the available release tooling and evidence in the order that best fits the
request. Do not assume that prepared notes or a successful build establish the
separate approval boundary.
