Index of every page on this site: llms.txt
All skills
hagaiw avatar

/release-action-boundary

@33ac0e9
Run it yourself

Use when a pull-request merge, release, or publication request needs its independent readiness and approval boundaries checked before action.

  • 3 files
  • 3.9 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/hagaiw/skillroll/release-action-boundary

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈42 tokens for metadata: the name and description. ≈237 when used: this file. ≈703 more on demand in 2 files.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈167 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 33ac0e9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 months ago

README badge

README badge for hagaiw/skillroll/release-action-boundary