Menu

Individual skill

prepare-repository-for-public-release

Use when asked to prepare a repository for public launch or open source it. Not for remote, credential, publish, deploy, or irreversible changes.

.devin/skills/prepare-repository-for-public-release/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
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)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Prepare repository for public release

## Contract

| Field | Bound contract |
|---|---|
| Trigger | The user asks to open source a project, prepare a repository for public launch, make an existing public project official, or establish release automation for that launch. |
| Authority | Reversible local: writes only named local artifacts (repository files, CI configs, documentation, packaging, release automation); rollback is version control. No remote mutation. Do not alter external visibility, remote state, credentials, or data-at-rest outside the repository. |
| Side effect | Prepare repository files, CI, documentation, packaging, and release automation; perform history and secret checks; stop before the external repository-visibility switch unless the human explicitly performs or authorizes it. |
| Done | A clean outsider clone can build, test, use, and contribute; secrets and confidential history are cleared through an appropriate fresh-repository decision; licensing and package metadata agree; CI and release automation are hardened; only the human-controlled visibility action remains. |

## Inputs

Required: the repository root, supplied by the current working directory or the human. Optional: organizational license policy and publishing accounts, supplied by the human when available.