agentleFS
Sign inStart free
metedatametedata/Remarc/.claude/skills/release-extension/SKILL.md

release-extension

Skill73 starsChanged 3 months agoMITView on GitHub

Package and release the Chrome extension - bump version, zip, publish as a GitHub Release, update web page

  • Deletes or force-pushes
  • Commits and pushes

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. Yorick-Ryu/deep-share★ 146same name
    2. tlennon-ie/neurodock★ 14same name
    3. akpmohan07/ai-context-bridge★ 4same 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.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Check current version: - Read extension/manifest.json to get the current version

    line 13
  2. Distinctive:

    Check what changed: - Run git log --oneline on the extension directory since the last version bump to see what's new:

    line 15
  3. Distinctive:

    Prompt for version: - Ask the user what version to release (suggest next patch/minor based on changes)

    line 20
  4. Very specific:

    Bump version: - Update version in extension/manifest.json

    line 22
  5. Very specific:

    Package: - Create a zip with the extension files inside a remarc-extension/ folder:

    line 24
  6. Very specific:

    Update web page: - Update website/public/chrome-extension/index.html:

    line 51
  7. Very specific:

    Update the download URL to https://github.com/metedata/Remarc/releases/download/extension-vVERSION/Remarc-Extension-VERSION.zip

    line 52
  8. Very specific:

    Update the version in the download-meta div

    line 53
  9. Distinctive:

    Clean up: - Remove temp files:

    line 64

“Common” is measured: kept by at least 6 in 10 of the 3 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

Release Chrome Extension

Package the Remarc Chrome extension and publish it as a GitHub Release on metedata/Remarc.

Steps

  1. Check current version - Read extension/manifest.json to get the current version
  2. Check what changed - Run git log --oneline on the extension directory since the last version bump to see what's new:
    git log --oneline -- extension/
  3. Prompt for version - Ask the user what version to release (suggest next patch/minor based on changes)
  4. Bump version - Update version in extension/manifest.json
  5. Package - Create a zip with the extension files inside a remarc-extension/ folder:
    mkdir -p /tmp/remarc-ext
rm -rf /tmp/remarc-ext/remarc-extension
cp -R extension/ /tmp/remarc-ext/remarc-extension/
cd /tmp/remarc-ext
zip -r Remarc-Extension-VERSION.zip remarc-extension/
  6. Commit and push the manifest bump first - so the release tag points at a commit containing the released source:
    git add extension/manifest.json
git commit -m "Release extension vVERSION"
git push

  7. Create the GitHub Release - on its own extension-v tag, and ALWAYS with --latest=false:

    gh release create extension-vVERSION /tmp/remarc-ext/Remarc-Extension-VERSION.zip \
  --repo metedata/Remarc \
  --title "Remarc Chrome Extension vVERSION" \
  --latest=false \
  --notes "- what changed"

    NEVER omit --latest=false. GitHub's releases/latest is repo-global; without the flag this release becomes "latest" and releases/latest/download/Remarc.zip (the app's /download redirect and README link) starts 404ing for every visitor and update check.

  8. Update web page - Update website/public/chrome-extension/index.html:
    • Update the download URL to https://github.com/metedata/Remarc/releases/download/extension-vVERSION/Remarc-Extension-VERSION.zip
    • Update the version in the download-meta div
  9. Verify:
    curl -sIL https://github.com/metedata/Remarc/releases/download/extension-vVERSION/Remarc-Extension-VERSION.zip | head -1
curl -sIL https://github.com/metedata/Remarc/releases/latest/download/Remarc.zip | head -1
    Both must return 200: the first proves the extension asset is live, the second proves the app's latest URL was not hijacked.
  10. Commit and push the web page change
  11. Clean up - Remove temp files:
    rm -rf /tmp/remarc-ext

Key Details

  • Tag pattern: extension-v{VERSION} - separate namespace from the app's v{VERSION} tags.
  • Download URL pattern: https://github.com/metedata/Remarc/releases/download/extension-v{VERSION}/Remarc-Extension-{VERSION}.zip
  • Web page: website/public/chrome-extension/index.html
  • Manifest: extension/manifest.json
  • Zip must contain a remarc-extension/ folder (not loose files) - users unzip and load this folder in Chrome
  • History: versions up to 0.3.0 were served from Cloudflare R2 (releases.remarc.app/Remarc-Extension-{VERSION}.zip); the old 0.3.0 zip stays there so existing links keep working

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