What 1.3.1 changes
AI HeroSkills v1.3.1After a bug fix, ask-matt now sends you to /retro
Version 1.3.1 is one fix, to the ask-matt router. Once diagnosing-bugs has fixed a bug, ask-matt now points you at retro, in the same session, to ask what would have prevented it. If you're upgrading from 1.2, the 1.3 line also brings three new skills, and one file rename you'll need to do yourself.
The line that changed
AI HeroSkills v1.3.1ask-matt's advice for something broken, before and after
Its post-mortem hands off to /improve-codebase-architecture when the real finding is that there's no good seam to lock the bug down.
Once the fix is in, run /retro in the same session to ask what would have prevented the bug; where the real finding is that there's no good seam to lock it down, that's a job for /improve-codebase-architecture.
Here's the line in ask-matt that changed. In 1.3.0 it still said diagnosing-bugs hands off to improve-codebase-architecture from its post-mortem. In 1.3.1 it tells you to run retro once the fix is in. And when the real finding is a missing seam, improve-codebase-architecture is a job you start yourself.
Why it changed
AI HeroSkills v1.3.1diagnosing-bugs stopped handing off in 1.3.0, and the router caught up
| The diagnosing-bugs docs page now says: if you're… | Reach for |
|---|---|
| Asking what would have prevented the bug, once it is fixed | retrorun in the same session |
| Facing a bug with no good seam to lock it down | improve-codebase-architecturewhich you start yourself |
The hand-off itself went away in 1.3.0. improve-codebase-architecture is user-invoked, so another skill can't start it, and diagnosing-bugs often runs unattended, so a failed call there could go unnoticed. ask-matt and the diagnosing-bugs docs page kept describing the old step. Now both agree: retro comes after the fix, and you start the architecture review yourself.
New in 1.3
AI HeroSkills v1.3.1Coming from 1.2? implement-spec, pr and retro join the plugin
If you're coming from 1.2, three skills graduate into the plugin. implement-spec builds a whole spec in one run, with subagents working the ready tickets in parallel. pr is the shape the agent gives a pull request body. And retro looks back at a session and suggests changes to the agent's environment, like new checks and coding standards. resolving-merge-conflicts is gone. The agent handles a merge or rebase conflict on its own now.
Fixed in 1.3
AI HeroSkills v1.3.1Six skills that npx skills couldn't list now install again
1.3 also fixes something you may have hit. These six skills had an unquoted colon in their description, which made the front matter invalid YAML. So skills.sh skipped them, and you couldn't list or install them with npx skills. They're quoted now. And skills that depend on another skill now say "call the Skill tool" with its name, which is meant to make that skill load more often.
The rename
AI HeroSkills v1.3.1Rename CONTEXT.md to GLOSSARY.md, or the skills stop reading it
This is the one change in 1.3 you have to act on. The domain glossary that grill-with-docs and domain-modeling keep is renamed, from CONTEXT.md to GLOSSARY.md, and the map file the same way. The skills only look for the new names now. So if your repo has the old file, git mv it after you upgrade, or the skills won't find your glossary.
Upgrade
AI HeroSkills v1.3.1Upgrade to 1.3.1
Upgrading takes one command, or none. If you installed with npx skills, run npx skills update. The Claude Code plugin updates itself. One thing to plan on a team: anyone still on 1.2 reads the old file name, so upgrade and rename the file together. After that, ask-matt sends you to retro once a bug is fixed. The full list is at aihero.dev slash skills.
