agentleFS
Sign inStart free
HoFireManHoFireMan/safe-public-release-skill/SKILL.md

safe-public-release

Skill0 starsChanged 2 months agoMITView on GitHub

Lightweight Pi Skill for preparing clean public releases from private Git repositories.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. serejaris/personal-corp-os★ 243same name
    2. serejaris/ris-claude-code★ 243same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use this Skill for a simple private-to-public workflow:

    line 8
  2. Distinctive:

    use Git tracked files as the source set.

    line 12
  3. Distinctive:

    run the project's tests when practical.

    line 16
  4. Distinctive:

    ask the user for explicit approval before any public mutation.

    line 18
  5. Distinctive:

    create a fresh public Git history rather than changing the private repository's remote or visibility.

    line 19
  6. Very specific:

    Before creating, pushing, or exposing a public repository, show the candidate inventory, test result, and SOURCE_HEAD, then obtain explicit …

    line 29
  7. Distinctive:

    If the requested public target already exists, stop and ask the user.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Safe Public Release V2

Use this Skill for a simple private-to-public workflow:

  1. inspect the private Git repository;
  2. require a clean working tree;
  3. use Git tracked files as the source set;
  4. apply the project's optional .publicignore;
  5. prepare a new temporary candidate;
  6. show its source HEAD and complete file inventory;
  7. run the project's tests when practical;
  8. warn or stop on obvious sensitive filenames;
  9. ask the user for explicit approval before any public mutation;
  10. create a fresh public Git history rather than changing the private repository's remote or visibility.

Prepare a candidate with:

python scripts/prepare_public.py --output /tmp/project-public

.gitignore controls what enters the private repository. .publicignore excludes tracked files from the public candidate. V2 supports blank lines, # comments, exact relative paths, directory rules ending in /, and simple Python fnmatch-style globs. It is not a full Git-ignore implementation. The private .publicignore file itself is not copied.

Before creating, pushing, or exposing a public repository, show the candidate inventory, test result, and SOURCE_HEAD, then obtain explicit user approval for that publication action. A candidate and passing tests do not authorize publication.

If the requested public target already exists, stop and ask the user. Never overwrite it, adopt unknown history, delete it, or force-push it automatically. Never force-push by default.

V2 is a preparation tool, not a provider API, secret-management system, release state machine, or automatic publisher. Its public distribution is MIT-licensed, Copyright (c) 2026 HoFireMan.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free