You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
A README badge.snapshot --badge <path> writes a shields.io endpoint file
(toolmenu | 12 tools · ~4.1K tokens · 2 warnings, red with errors, yellow with
warnings) and prints the README line, which reads it from GitHub on the default
branch. Committed with the baseline, it changes when the baseline does. toolmenu's
README shows its own MCP server's.
SARIF output, for GitHub code scanning.--sarif <path> writes the findings
of snapshot, diff or session as SARIF 2.1.0 beside the usual report; --format sarif prints it instead. Each result points at the menu file, at the line
of the tool it's about (--sarif-menu names the committed one when the menu was
written elsewhere), with a fingerprint from its rule and tool (and which of that
rule's findings on the tool it is) so alerts track across runs. The Action's new sarif input writes snapshot.sarif, diff.sarif and session.sarif into a folder for github/codeql-action/upload-sarif.
Plugin: two more skills, and evals.release-check (before tagging or
publishing: what changed since the last release, what breaks clients, the bump it
needs) and setup-ci (adds toolmenu to CI with toolmenu init). check-mcp-menu
names more of the moments it's for (a rename, a description edit, an agent picking
the wrong tool) and falls back to the CLI without the MCP tools. plugins/toolmenu/evals/ has seven cases for claude plugin eval: each skill fires
on its own prompts (3 of 3 runs, 0 of 3 without the plugin), none fires on unrelated
work, and setup-ci gives the right init command for a scaffolded project.