agentleFS
Jamie-BitFlightJamie-BitFlight/claude_skills/.agents/skills/daily-releases/SKILL.md

daily-releases

Skill67 starsChanged 54 days agoMITView on GitHub

Use when creating or backfilling AI-categorized daily GitHub releases from branch commits.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the bundled controller from the target repository root.

    line 10
  2. Very specific:

    When advance returns awaiting_worker, dispatch all returned tasks up to concurrency.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

<release_args>$ARGUMENTS</release_args>

Daily Releases

Run the bundled controller from the target repository root. Resolve this skill's directory as <skill-root>; do not assume an installation path. Every invocation writes one compact JSON object to stdout and diagnostics to stderr.

uv run "<skill-root>/scripts/daily_releases.py" prepare \
  [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD] [--branch BRANCH] \
  [--repo OWNER/REPO] [--dry-run] [--token-limit N]

This outputs a JSON object: {"run":"…","state":"prepared"}. It persists immutable inputs and task records under daily-releases/<run-id>/. Without --start-date, discovery resumes after the newest daily release; use an explicit date for backfills.

uv run "<skill-root>/scripts/daily_releases.py" advance --run <run-id>

When advance returns awaiting_worker, dispatch all returned tasks up to concurrency. A task is only its id, input, artifact, model, and pending status. Workers follow references/worker_process.md, read only their input, atomically write their artifact, and return only STATUS: DONE plus its path. Re-run advance after workers complete. It fans out ready buckets, then emits synthesis only after every bucket artifact validates for this run.

uv run "<skill-root>/scripts/daily_releases.py" publish --run <run-id>

Each call fans out all ready days up to its returned concurrency limit. It deterministically finalizes title, summary, and statistics, renders notes, validates every receipt against the remote release and tag identity, and persists independent status artifacts. Re-run after interruptions; only failed or unverified days retry.

Reference files

  • scripts/daily_releases.py — controller
  • references/worker_process.md — worker boundary and artifact identity
  • scripts/run_tests.py — bundled verification

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.