agentleFS
coredevicescoredevices/PebbleOS/.agents/skills/release/SKILL.md

release

Skill1.5k starsChanged 3 days agoApache-2.0View on GitHub

Use when cutting a PebbleOS release, either a new version from main or a fix release from a release branch (vX.Y-branch). Covers the hardware itest gate, tag naming, signed annotated tags and what CI does on tag push.

  • Commits and pushes

193 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 2 mentionsMar 2026: 2 mentionsApr 2026: 6 mentionsMay 2026: 4 mentionsJun 2026: 5 mentionsJul 2026: 9 mentionsAug 2026: 2 mentionsSep 2026: 4 mentionsOct 2026: 11 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the coredevices/PebbleOS repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about coredevices/PebbleOS

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Hacker News (51 times).

On GitHub · 50

45 more on GitHub

On Hacker News · 1

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check the latest tags first:

    line 20
  2. Very specific:

    If the branch does not exist yet, create it from the release tag and push it upstream: git push upstream vX.Y.0:refs/heads/vX.Y-branch.

    line 32
  3. Distinctive:

    Only fixes go on a release branch.

    line 38
  4. Very specific:

    Before tagging, run the hardware integration test workflow (hw-itest.yml) on the exact commit you will tag, and wait until every job passes.

    line 42
  5. Very specific:

    Check that the run's headSha is the commit you will tag.

    line 53
  6. Distinctive:

    Never move or delete a tag after you push it.

    line 72
  7. Distinctive:

    Check that the GitHub release has the files and that "latest" is set only for releases from main.

    line 83

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “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

Releasing PebbleOS

A release is a signed, annotated v* tag pushed to coredevices/PebbleOS (the upstream remote). Pushing the tag is the release: release.yml builds everything, publishes the GitHub release and uploads to eng-dash. There is no version file to bump; the firmware version is git describe.

Tagging scheme

ReleaseTagged fromTag
New versionmainvX.Y.0, Y one above the latest vX.Y.*
Fix releasevX.Y-branchvX.Y.Z, Z one above the latest on that branch

Check the latest tags first:

git fetch upstream --tags
git tag --sort=-v:refname | head

Where the release comes from

  • New versions are tagged from main, never from a branch. The release job marks a release as GitHub's "latest" only when the tag is on main.
  • Fix releases are tagged from release branches vX.Y-branch.
    • If the branch does not exist yet, create it from the release tag and push it upstream: git push upstream vX.Y.0:refs/heads/vX.Y-branch.
    • Fixes land on main first. They get to the branch as cherry-pick -x commits, ideally by putting a backport-vX.Y-branch label on the merged main PR. backport.yml then opens the backport PR.
    • Only fixes go on a release branch. Features do not.

1. Hardware integration tests must be green

Before tagging, run the hardware integration test workflow (hw-itest.yml) on the exact commit you will tag, and wait until every job passes. A green nightly run also counts if it tested the same SHA you will tag.

gh workflow run hw-itest.yml -R coredevices/PebbleOS --ref main      # or vX.Y-branch
gh run list -R coredevices/PebbleOS --workflow hw-itest.yml -L 3     # find the run
gh run watch -R coredevices/PebbleOS <run-id> --exit-status
  • Check that the run's headSha is the commit you will tag. If the branch moves while the tests run, run them again or tag the commit that was tested.
  • Any failure stops the release. Find out why before tagging. Do not rerun until it goes green. A flake you have already seen elsewhere is the one exception, and you have to say so.

2. Tag

Tags must be annotated and signed. The message is the tag name.

git fetch upstream
git tag -s vX.Y.Z -m vX.Y.Z <tested-sha>
git verify-tag vX.Y.Z
git push upstream vX.Y.Z
  • Tag the tested SHA explicitly, not whatever a local branch points to.
  • Never move or delete a tag after you push it. If something is wrong, make a new release.
  • Pushing a tag cannot be undone. Get the user's confirmation before pushing.

3. After the tag push

  • Watch the Release workflow: gh run list -R coredevices/PebbleOS --workflow release.yml -L 1. It builds the firmware, the PRF, the QEMU and native builds, then makes the GitHub release with all artifacts and publishes to eng-dash.
  • Check that the GitHub release has the files and that "latest" is set only for releases from main.
  • Post release notes to Slack #releases when the user asks:
    • The main message has simple notes for users.
    • The technical notes go in a thread reply.
    • Draft both from git log <previous-tag>..vX.Y.Z.

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.