openmeld-changelog
Skill1.4k starsChanged 6 days agoMITView on GitHub
Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating generated Changelog files, or historically backfilling missing changes.
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- amplifthq/opentagword for word, first seen Oct 25, 2026
Who's talking about amplifthq/openmeld
- sudosubin/agents.nix“agent-skills.github.amplifthq.openmeld: 0.3.294 → 0.3.295”GitHub · Nov 13, 2026
- sudosubin/agents.nix“agent-skills.github.amplifthq.openmeld: 0.3.293 → 0.3.294”GitHub · Nov 12, 2026
- sudosubin/agents.nix“agent-skills.github.amplifthq.openmeld: 0.3.291 → 0.3.293”GitHub · Nov 11, 2026
- sudosubin/agents.nix“agent-skills.github.amplifthq.openmeld: 0.3.290 → 0.3.291”GitHub · Nov 6, 2026
- sudosubin/agents.nix“agent-skills.github.amplifthq.openmeld: 0.3.288 → 0.3.290”GitHub · Nov 3, 2026
The biggest 5 of 31 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 31
Talked about on GitHub (31 times).
On GitHub · 31
- Nov 13, 2026agent-skills.github.amplifthq.openmeld: 0.3.294 → 0.3.295 — sudosubin/agents.nix0 reactions
- Nov 12, 2026agent-skills.github.amplifthq.openmeld: 0.3.293 → 0.3.294 — sudosubin/agents.nix0 reactions
- Nov 11, 2026agent-skills.github.amplifthq.openmeld: 0.3.291 → 0.3.293 — sudosubin/agents.nix0 reactions
- Nov 6, 2026agent-skills.github.amplifthq.openmeld: 0.3.290 → 0.3.291 — sudosubin/agents.nix0 reactions
- Nov 3, 2026agent-skills.github.amplifthq.openmeld: 0.3.288 → 0.3.290 — sudosubin/agents.nix0 reactions
26 more on GitHub
- Nov 2, 2026agent-skills.github.amplifthq.openmeld: 0.3.284 → 0.3.288 — sudosubin/agents.nix0 reactions
- Nov 1, 2026agent-skills.github.amplifthq.openmeld: 0.3.281 → 0.3.284 — sudosubin/agents.nix0 reactions
- Oct 29, 2026agent-skills.github.amplifthq.openmeld: 0.3.279 → 0.3.281 — sudosubin/agents.nix0 reactions
- Oct 29, 2026agent-skills.github.amplifthq.openmeld: 0.3.278 → 0.3.279 — sudosubin/agents.nix0 reactions
- Oct 28, 2026agent-skills.github.amplifthq.openmeld: 0.3.276 → 0.3.278 — sudosubin/agents.nix0 reactions
- Oct 28, 2026agent-skills.github.amplifthq.openmeld: 0.3.274 → 0.3.276 — sudosubin/agents.nix0 reactions
- Oct 28, 2026agent-skills.github.amplifthq.openmeld: 0.3.273 → 0.3.274 — sudosubin/agents.nix0 reactions
- Oct 26, 2026agent-skills.github.amplifthq.openmeld: 0.3.272 → 0.3.273 — sudosubin/agents.nix0 reactions
- Oct 23, 2026agent-skills.github.amplifthq.openmeld: 0.3.271 → 0.3.272 — sudosubin/agents.nix0 reactions
- Oct 22, 2026agent-skills.github.amplifthq.openmeld: 0.3.270 → 0.3.271 — sudosubin/agents.nix0 reactions
- Oct 22, 2026agent-skills.github.amplifthq.openmeld: 0.3.267 → 0.3.270 — sudosubin/agents.nix0 reactions
- Oct 21, 2026agent-skills.github.amplifthq.openmeld: 0.3.264 → 0.3.267 — sudosubin/agents.nix0 reactions
- Oct 17, 2026[Candidate] amplifthq/openmeld/release/openmeld-cli-skill - openmeld-cli — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 16, 2026agent-skills.github.amplifthq.openmeld: 0.3.263 → 0.3.264 — sudosubin/agents.nix0 reactions
- Oct 16, 2026[Candidate] amplifthq/openmeld/.claude/skills/release-runbook - release-runbook — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 16, 2026[Candidate] amplifthq/openmeld/.claude/skills/openmeld-changelog - openmeld-changelog — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 16, 2026[Candidate] amplifthq/openmeld/.claude/skills/docs-lifecycle-scan - docs-lifecycle-scan — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 16, 2026agent-skills.github.amplifthq.openmeld: init at 0.3.263 — sudosubin/agents.nix0 reactions
- Oct 15, 2026[Candidate] amplifthq/openmeld/.agents/skills/writing-tests - writing-tests — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 15, 2026[Candidate] amplifthq/openmeld/.agents/skills/react-doctor - react-doctor — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 15, 2026[Candidate] amplifthq/openmeld/.agents/skills/postgresql-planning - postgresql-planning — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 15, 2026[Candidate] amplifthq/openmeld/.agents/skills/openmeld-changelog - openmeld-changelog — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 15, 2026[Candidate] amplifthq/openmeld/.agents/skills/fixing-flaky-tests - fixing-flaky-tests — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 15, 2026[Candidate] amplifthq/openmeld/.agents/skills/debugging-ci-failures - debugging-ci-failures — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 7, 2026feat: share selected connection health and bounded native API reads — amplifthq/open-connector0 reactions · 2 comments
- Oct 6, 2026feat: support selected GitHub connections for Git streams — amplifthq/open-connector0 reactions · 1 comment
Other versions1 project uses a version of this.
Word for word · 1
- amplifthq/opentag★ 1.4k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- debugging-ci-failuresSkill
- fixing-flaky-testsSkill
- postgresql-planningSkill
- react-doctorSkill
- verify-remote-agent-executionSkill
- verify-runtime-coordinator-livenessSkill
- verify-service-connectionSkill
- verify-wake-progressSkill
- writing-testsSkill
- docs-lifecycle-scanSkill
- openmeld-changelogSkill
- release-runbookSkill
- wake-traceSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Keep changelog/entries/*.md as the human- and agent-authored source of truth.
- Very specific: line 9
Treat CHANGELOG.md, changelog/index.json, and changelog/releases/*.md as generated projections.
- Very specific: line 18
Publish a change: add publishedAt, optional release, and concrete evidence only after the delivery claim is proven.
- Distinctive: line 29
Use the coding agent's native file, Git, GitHub, test, and search tools.
- Very specific: line 62
Use a unique lowercase slug for both the filename and id.
≈ “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.
Files
OpenMeld Changelog
Keep changelog/entries/*.md as the human- and agent-authored source of truth.
Treat CHANGELOG.md, changelog/index.json, and changelog/releases/*.md as
generated projections. Read developing/engineering/changelog.md before
editing either source or projections.
Choose the job
- Record a change: inspect the implementation and add one concise draft entry when users or contributors gain, lose, or materially experience a capability.
- Publish a change: add
publishedAt, optionalrelease, and concreteevidenceonly after the delivery claim is proven. - Backfill history: reconstruct an omitted entry from tags, commits, pull requests, tests, deployment records, or other durable evidence. Use the original availability date, not today's date.
- Prepare release notes: publish the applicable entries, rebuild the projections, and hand the generated release file to the authorized release workflow. A notes file is not release authorization.
Gather evidence
Use the coding agent's native file, Git, GitHub, test, and search tools. No custom Changelog command is required for investigation or writing.
Establish these facts separately:
- what behavior changed;
- who can notice or use it;
- which code, pull request, or commit contains it;
- whether it was merged;
- whether the relevant component was delivered; and
- whether any required real-user smoke produced the visible outcome.
Merge, tag, deployment, and smoke are different claims. Keep an entry draft when the evidence proves only an earlier claim.
Decide whether to record it
Record changes that affect users, operators, integrators, or contributors:
- new or removed capabilities;
- material workflow or behavior improvements;
- user-visible fixes and security changes;
- breaking behavior and deprecations; or
- developer-facing changes that alter supported integration or contribution work.
Skip internal refactors, test-only changes, routine dependency maintenance, and documentation cleanup when they do not change an external workflow. Combine several implementation commits into one user-meaningful entry when they deliver one outcome.
Write the entry
Use a unique lowercase slug for both the filename and id. Write native-level
English for OpenMeld's North American audience. Lead with what is now possible
or what changed, not implementation details.
---
id: slack-channel-invitations
title: Invite teammates from Slack
kind: new
areas: ["channels", "center-agent"]
audiences: ["admins"]
---
Organization admins can invite a teammate while working with the Center Agent
in Slack, without switching to a separate setup flow.That entry is a draft. Publish it only after delivery is proven:
publishedAt: 2026-08-17
release: v0.3.60
evidence: ["pr:72", "commit:1d5254d", "workflow:123456789"]release is optional for continuously delivered changes. Every published entry
requires durable evidence. Keep uncertain historical work as a draft rather
than inventing a date, scope, or release.
Rebuild and verify
Run:
pnpm changelog:build
pnpm changelog:checkReview the resulting diff. A complete change has valid source entries, up-to-date deterministic projections, and no unsupported publication claim.
For a historical backfill, also confirm that adding the older entry placed it
by publishedAt rather than by the date of the backfill commit.
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.

