Repository navigation
Releases
Releases · ismayilkarimli/MergeAtlas
MergeAtlas 0.6.3
Changed
SKILL.mdnames the script asscripts/mergeatlas.py, its place in the skill folder, and tells the agent to run it by its full path, where it wrote${CLAUDE_SKILL_DIR}, which only Claude Code fills in. Other agents no longer have to work out what the variable means. Claude Code's pre-approval inallowed-toolsis unchanged.
MergeAtlas 0.6.2
Changed
- The skill pre-approves only its own script, as
Bash(${CLAUDE_SKILL_DIR}/scripts/mergeatlas.py *), where it allowed anypython3,pythonorpycommand. The script runs as a program of its own, soSKILL.mdcalls it by its path and names no interpreter; where that fails, as it can on Windows, the agent putspython3,pythonorpyin front, and Claude Code asks before running it.
MergeAtlas 0.6.1
Changed
- The marketplace installs the plugin from ismayilkarimli/mergeatlas-plugin, which holds the plugin alone: its manifest, the skill, a README and the license. Each release copies
plugin/there as one commit naming the commit it came from, and that repository refuses every other change. A company marketplace can list that repository with a plaingithubsource pinned to a release tag.
MergeAtlas 0.6.0
Added
- A company's own plugin marketplace can list MergeAtlas with a
git-subdirsource pointed atplugin/and pinned to a release tag, and Claude Code fetches that folder alone: the plugin manifest,SKILL.md, the script, the viewer and the license. The README shows the entry. - Each release carries
mergeatlas-<version>.zip, the skill folder alone, with its SHA-256 beside it, for teams that vendor the skill into their own repository.python3 tools/build_dist.pybuilds the same zip from a clone, byte for byte. SKILL.mddeclares its license, what it needs to run, and the tools it uses, among them AskUserQuestion for choosing the cold readers' model.
Changed
- The skill moved from
skills/mergeatlastoplugin/skills/mergeatlas. If you linked it into your skills folder by hand, link the new path. The plugin finds it there by itself. - The script builds every command it runs as a list before running it, and none goes through a shell.
MergeAtlas 0.5.0
Added
- Windows. The script runs itself in Python's UTF-8 mode there, so diffs and PR text in any language read and print as on macOS and Linux, and the viewer server keeps running after the command that started it ends.
- GitLab merge requests, on gitlab.com or a self-hosted GitLab, are mapped as pull requests are, through the
glabCLI. A merge request link works for fetch, a stack of merge requests is found from the branches they target, and the viewer says "merge request", writes!7and opens diff lines in GitLab's own diff where it can.
Changed
- A map's id now names its host, such as
github-owner-repo-12andgithub-owner-repo-stack-7, and the viewer takes every address it opens, and the name of the host it shows, from the map. Maps from earlier releases have no such addresses, so publish them again. - fetch takes a pull request's diff and its file list with their added and removed lines from your clone, where it asked GitHub for them, so a very large pull request no longer fails on a diff GitHub will not send.
Removed
- The code that kept maps and servers from earlier releases working: a map in the format from before cards held changes is no longer set aside by itself, and a viewer server that names no release is left running with a note instead of being looked up and replaced.
MergeAtlas 0.4.0
Added
- Every code link is checked against the lines it points at.
claimswrites each link's words and lines to a file for a checker, andcheckedrecords the links that hold. A link is checked again only when its words or its lines change. - A fixed set of three pull requests, in
evals/, to measure a change to the skill against: what a map costs, how many of its links a checker rejects, and how many fixed questions it answers.
Changed
- A first map is cold read in two rounds, where it took three. From the second round on, and on an update, a reader is asked only about the sentences written or edited since the card was last read.
- A card that only lost sentences passes without a reader.
reportsays how many links were checked and how many were sent back.
MergeAtlas 0.3.0
Added
- When a mapped pull request gets new commits, fetch writes a delta file holding only what changed since the last map, and the agent reads that in place of the whole diff.
- A map is now reused change by change: fetch sends back the single changes whose key lines left the diff, lists the changes and arrows whose links to check because a line they link to changed, counts the lines that entered and left each card's diff, and lists the story, intents and arrows to check beside them.
- Fetch runs a changed pull request's logged searches again at the new head and reports the files that newly match or no longer match.
readerswrites each unread card to a file for its cold reader, andpassedrecords the cards a reader found nothing in, so a card is read again only when its words change.fetch --freshmaps a pull request again from scratch. A map in a format too old to show starts over by itself.- A map updated for new commits says which commit it was updated from and marks the cards the new commits changed until you open them. The notice counts the cards still to open.
- An update is cold read in one round, and only on the statements written or edited for it.
Changed
- The cold reader's instructions now live in the script, and the agent hands each reader a file path where it used to paste the card.
- When more than half of a map's changes would be rewritten, fetch says to map the pull request afresh.
reportsays how many of a changed map's changes were sent back.