#2 (fix): handle binary assets in /ak:commit skill

[bezael]

Objective

The /ak:commit skill failed or produced malformed commit messages when staged files included binary assets (images, fonts, compiled files). Without explicit handling, the model had no file names or semantic context when all staged content showed only as Binary files a/... and b/... differ.

Bug Fixes

• Add git diff --staged --name-status to the skill context so binary file names and statuses are always available, even when diff content is absent
• Add a rule instructing the model to use --name-status output to describe binary files and never omit them from the commit message
• Apply the same fix to antigravity-skills/commit/SKILL.md for Google Antigravity / Gemini users
• Recreate skills/commit/SKILL.md in the new frontmatter format (ak:commit, disable-model-invocation, allowed-tools) so the CLI installer picks it up again

Tests

• Add evals/fixtures/sample-diffs/chore-add-assets.diff — a realistic diff with two binary files (logo.png, inter.woff2) and a text change
• Add a binary-assets test case to evals/skills/commit.eval.js with an extra rubric criterion verifying binary filenames are not silently dropped from the message
• Extend runCommitEval to accept extraCriteria so individual test cases can inject additional rubric checks

Related

#2