agentleFS
Sign inStart free
adezeadeze/raindrop-mcp/.github/skills/publishing/SKILL.md

publishing

Skill188 starsChanged 8 months agoMITView on GitHub

Publishing and release workflow with semantic-release and GitHub Actions

  • Reads credentials

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    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
  1. Distinctive:

    Use this workflow for all standard releases in this repository.

    line 8
  2. Distinctive:

    No long-lived npm token is required for the standard CI release path.

    line 31
  3. Distinctive:

    Do not manually bump package versions for standard releases.

    line 50
  4. Distinctive:

    Do not manually create release tags for standard releases.

    line 51
  5. Distinctive:

    Do not run manual npm publish commands for standard releases.

    line 52
  6. Very specific:

    Keep release behavior in .releaserc.json and CI workflow aligned.

    line 53

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

Publishing Skill for @adeze/raindrop-mcp

Use this workflow for all standard releases in this repository.

Source of Truth

  • Release command: bun run release
  • Release config: .releaserc.json
  • CI trigger: .github/workflows/ci.yml on push to master

Standard Release Flow

  1. Merge Conventional Commit-based changes to master.
  2. CI runs lint, type-check, tests, and build.
  3. CI release job runs semantic-release.
  4. semantic-release computes version, updates CHANGELOG.md, tags release, publishes npm, and creates a GitHub Release.
  5. Release prepare step syncs manifest.json and builds raindrop-mcp.mcpb so the bundle is attached to the GitHub Release.

Required Secrets

  • GITHUB_TOKEN: provided by GitHub Actions.

Publishing Authentication

  • npm publish uses GitHub Actions OIDC trusted publishing.
  • No long-lived npm token is required for the standard CI release path.

Local Verification Before Merge

bun run lint
bun run type-check
bun run test
bun run build

Conventional Commit Examples

  • fix: handle missing collection id in bulk edit
  • feat: add includeArchived filter to bookmark_search
  • feat!: remove deprecated query parameter

Rules

  • Do not manually bump package versions for standard releases.
  • Do not manually create release tags for standard releases.
  • Do not run manual npm publish commands for standard releases.
  • Keep release behavior in .releaserc.json and CI workflow aligned.

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