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
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Who's talking about coredevices/PebbleOS
- coredevices/mobileapp“Add in blood oxygen support into the mobile app.”GitHub · Jun 24, 2026 · 5 reactions
- pebble-dev/pebble-firmware“MenuLayer: scroll wrap around and vibes”GitHub · Dec 23, 2025 · 5 reactions
- coredevices/mobileapp“Day/night backlight color”GitHub · Jun 23, 2026 · 2 reactions
- A Hacker News story“PebbleOS”Hacker News · Jun 21, 2026 · 2 points
- matejdro/microPebble“Automatic firmware update”GitHub · Nov 15, 2025 · 2 reactions
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
- Jun 24, 2026Add in blood oxygen support into the mobile app. — coredevices/mobileapp5 reactions · 11 comments
- Dec 23, 2025MenuLayer: scroll wrap around and vibes — pebble-dev/pebble-firmware5 reactions · 5 comments
- Jun 23, 2026Day/night backlight color — coredevices/mobileapp2 reactions · 8 comments
- Nov 15, 2025Automatic firmware update — matejdro/microPebble2 reactions
- Jun 24, 2026Enable blood oxygen support + change values around — coredevices/pebbleos-nonfree1 reaction · 2 comments
45 more on GitHub
- Apr 26, 2026Add support for iOS Notifications Filter — coredevices/mobileapp1 reaction · 2 comments
- Jan 12, 2026notifications: iOS support for custom icon/vibe/color — coredevices/mobileapp1 reaction · 1 comment
- Nov 26, 2025Add notification icons and colors for EU neobank apps — coredevices/mobileapp1 reaction
- Nov 6, 2026Stop waiting forever for the emulator's firmware — coredevices/cloudpebble0 reactions · 2 comments
- Nov 6, 2026Stop waiting forever for the emulator's firmware — coredevices/pebble-tool0 reactions
- Oct 30, 2026Sideloading the same version of an app with the microphone permission leaves the old binary on the watch — coredevices/mobileapp0 reactions
- Oct 25, 2026Diagnostics v2: settings, "did you feel it?", stillness, last 10 sessions — nicolinux/silent-sit-pebble0 reactions
- Oct 20, 2026Button cues when in "left-handed mode" — Sykero-Software/PebbleCountdownTimer0 reactions · 1 comment
- Oct 16, 2026pebble: define the XS FFI syscalls with PBL_SYSCALL — Moddable-OpenSource/moddable0 reactions · 1 comment
- Oct 16, 2026pebble: harden the XS FFI syscall boundary — Moddable-OpenSource/moddable0 reactions · 1 comment
- Oct 16, 2026pebble: drop an unused kernel/util/sleep.h include — Moddable-OpenSource/moddable0 reactions · 2 comments
- Oct 14, 2026PebbleOS: PBLBOOTのRecovery OTA転送が通常OSの起動選択に混入する — zunda-pixel/pebble-app0 reactions
- Oct 14, 2026PebbleOS: Recovery更新前にイメージの領域サイズと整数オーバーフローを検証していない — zunda-pixel/pebble-app0 reactions
- Oct 8, 2026pebble: use struct pbl_tm for c_tm — Moddable-OpenSource/moddable0 reactions · 1 comment
- Oct 6, 2026pebble: exit the app instead of rebooting on fatal errors — Moddable-OpenSource/moddable0 reactions · 9 comments
- Oct 2, 2026pebble: handle the SpO2 health event — coredevices/moddable0 reactions
- Sep 13, 2026Implement everything as a watchapp — OpenMinimed/PebbleOS0 reactions
- Sep 13, 2026Music: add watch output device selection — coredevices/mobileapp0 reactions · 4 comments
- Sep 8, 2026bluetooth-fw/nimble: reset GATT resource counters on host restart — embedder-dev/PebbleOS0 reactions
- Sep 5, 2026Link Checker Report — nschonni/PebbleOS0 reactions
- Aug 30, 2026Voice Assistant UI improvements — skylord123/pebble-home-assistant-ws0 reactions
- Aug 25, 2026Implement Pebble companion app — zunda-pixel/pebble-app0 reactions
- Jul 31, 2026hal: keep VBAT_LDO at 3.3V to preserve RTC during hibernate — coredevices/SiFli-SDK0 reactions · 2 comments
- Jul 31, 2026Battery optimization — OpenMinimed/PebbleOS0 reactions · 4 comments
- Jul 23, 2026Update repo table — arran4/arran40 reactions
- Jul 21, 2026Update repo table — arran4/arran40 reactions
- Jul 20, 2026Update repo table — arran4/arran40 reactions
- Jul 17, 2026Update repo table — arran4/arran40 reactions
- Jul 16, 2026Update repo table — arran4/arran40 reactions
- Jul 16, 2026Show alarm — mxmehl/pebble-clean-overview0 reactions
- Jul 13, 2026Update repo table — arran4/arran40 reactions
- Jun 30, 2026Update repo table — arran4/arran40 reactions
- May 26, 2026Music App Prefs: Allow disabling priority in launcher, configure vibe strength — coredevices/mobileapp0 reactions · 3 comments
- May 19, 2026iOS find phone — coredevices/mobileapp0 reactions · 7 comments
- May 7, 2026Add Gentle vibe option to WatchPrefEntity — coredevices/mobileapp0 reactions · 1 comment
- May 3, 2026settings_quick_launch: combo hold up + down — coredevices/mobileapp0 reactions · 1 comment
- Apr 27, 2026Stop stripping patch version from package.json during build — coredevices/pebble-tool0 reactions
- Apr 26, 2026broken semver support; pebble build strips the patch version from the built .pbw — coredevices/pebble-tool0 reactions · 2 comments
- Apr 15, 2026Dockerfile missing librsvg2-bin dependency — pebble-dev/pebbleos-docker0 reactions
- Apr 15, 2026Clarify compass calibration and peek behaviour — coredevices/sdk-docs0 reactions · 1 comment
- Apr 4, 2026Add Music player settings — coredevices/mobileapp0 reactions · 1 comment
- Mar 30, 2026Allow overriding webpack config — coredevices/pebble-tool0 reactions
- Mar 13, 2026Add Hebrew (he_IL) language pack — coredevices/mobileapp0 reactions · 1 comment
- Feb 22, 2026settings_quick_launch: new combo back + up — coredevices/mobileapp0 reactions
- Feb 16, 2026fw/freertos/cm33: add PSPLIM to task context save/restore — coredevices/FreeRTOS-Kernel0 reactions
On Hacker News · 1
- Jun 21, 2026PebbleOS2 points
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.
MicrosoftSkillcreate-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
GrinvSkillchangelog-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
GrinvSkilldocs-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 AzureSkillcomponent-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 AzureSkilldocumentation-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-devSkilllaunch-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
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
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.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pr-reviewSkill
- working-with-qemuSkill
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
- Distinctive: line 20
Check the latest tags first:
- Very specific: line 32
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.
- Distinctive: line 38
Only fixes go on a release branch.
- Very specific: line 42
Before tagging, run the hardware integration test workflow (hw-itest.yml) on the exact commit you will tag, and wait until every job passes.
- Very specific: line 53
Check that the run's headSha is the commit you will tag.
- Distinctive: line 72
Never move or delete a tag after you push it.
- Distinctive: line 83
Check that the GitHub release has the files and that "latest" is set only for releases from main.
“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.
Files
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
| Release | Tagged from | Tag |
| New version | main | vX.Y.0, Y one above the latest vX.Y.* |
| Fix release | vX.Y-branch | vX.Y.Z, Z one above the latest on that branch |
Check the latest tags first:
git fetch upstream --tags
git tag --sort=-v:refname | headWhere 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 onmain. - 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
mainfirst. They get to the branch ascherry-pick -xcommits, ideally by putting abackport-vX.Y-branchlabel on the mergedmainPR.backport.ymlthen opens the backport PR. - Only fixes go on a release branch. Features do not.
- If the branch does not exist yet, create it from the release tag and
push it upstream:
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
headShais 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
Releaseworkflow: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
#releaseswhen 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.
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
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.

