Skip to content

v1.2.0

Choose a tag to compare

View all tags
@kgilpin kgilpin released this 02 Sep 15:33
· 32 commits to main since this release
v1.2.0
316be59

What's new

appmap-label is now appmap-config

The skill is renamed and rewritten against each agent's source. It is now the one place for everything about appmap.yml and labels:

  • The default appmap.yml each agent writes, and a starting config per language that changes as little as possible from it.
  • What exclude: matches in each agent. Ruby matches file path substrings under a package and class names at the top level. Python matches dotted names relative to the package path. Node matches file path substrings, function names, or Class.method. Java matches package, class, or Class.method names by prefix. This differs per agent and is the most common mistake.
  • A label attaches to a function that is already being recorded, so packages: and exclude: come first.
  • The label taxonomy, the "Cutting noise" rules, and the YAML rule to quote method ids containing #.

The other skills point at appmap-config instead of repeating it. appmap-review drops its copy of the taxonomy. appmap-gold-traces drops its copies of the exclude syntax and layout advice. appmap-record drops stale references to skills that no longer exist and gains an "Output directory" section with the per-agent rules for appmap_dir.

If you symlinked appmap-label into ~/.claude/skills, replace the link:

rm ~/.claude/skills/appmap-label
ln -s "$PWD/appmap-config" ~/.claude/skills/appmap-config

appmap-setup is split in two

  • appmap-setup now covers recording only: environment checks, build and test as-is, one unit recording, one integration recording, noise pruning, and a repo-local skill with the working commands. It works on whatever commit is checked out and names the three commits it leaves behind so other workflows can cherry-pick them.
  • appmap-setup-review is new. It chooses BASE and HEAD commits one feature apart, runs appmap-setup on BASE, seeds gold traces, replays the commits onto HEAD, updates the gold traces, and runs appmap-review. It is a demonstration and evaluation workflow and says so, so it does not trigger for plain setup requests.
  • Cross-skill references use phase headings and commit names, never numbers.

appmap-review

The SQL pass now says to use the recorded query text to confirm what a performance fix claims. A LIMIT pushed down into the database shows up in the query, and a fix whose query text did not change did not do what its commit message says.

Full changelog: v1.1.0...v1.2.0

Assets 2
Loading