Skip to content

Releases: ota-meshi/agent-customization-inspector

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 11 Sep 00:36
b290f39

Minor Changes

  • #19 25ee324 Thanks @ota-meshi! - Add Antigravity CLI as a fourth supported tool. The inventory now lists the files Antigravity CLI reads — the root GEMINI.md and AGENTS.md, the skills, custom agents, and MCP servers under .agents/, and, after consent, the context file, MCP servers, custom agents in both documented shapes, skills in both documented shapes, settings, permissions, and hooks of the ~/.gemini home — and names Antigravity CLI as a reader of the files it shares with the other tools.

Patch Changes

  • #19 25ee324 Thanks @ota-meshi! - Compute every source comparison with VS Code's own line diff (vscode-diff) in place of a hand-assembled Myers pass. A line the other copy kept at another indentation now stands opposite that line instead of opposite whatever took its position, and the mark on it is the two spaces it gained rather than both sides' whole indentation. Within a line, a mark no longer breaks into islands around a . or a / that two otherwise unrelated values happen to share.

  • #19 25ee324 Thanks @ota-meshi! - Keep every hook declaration a carrier makes. A declaration whose hook or event a file named __proto__ reached the comparison as an empty document, and two declarations whose hook names differ only by where a NUL sits collapsed into one on the detail page. Both are now published as written.

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 09 Sep 10:48
f176e7f

Patch Changes

  • #15 4a92fc5 Thanks @ota-meshi! - The skill detail's "Other copies of this skill" strip is now the last row of its invocation name's box — inset like the recognition rows above it and parted from them by the same hairline — instead of sitting against the box's border. On every detail page, the strip's label is now centred on the line with the entries beside it rather than sitting above their text.

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 09 Sep 09:58
dd77af6

Minor Changes

  • #13 ea6a054 Thanks @ota-meshi! - A Claude Code skill at the selected root is now listed under the name its frontmatter declares — the name Claude Code's own slash menu and the desktop app list it under — with the skill directory as the fallback, so a root SKILL.md that Claude Code and GitHub Copilot both read is one row rather than two. A nested skill keeps its directory-qualified command, such as apps/web:deploy.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 09 Sep 07:32
c37c10d

Minor Changes

  • #11 910c72a Thanks @ota-meshi! - Source is now coloured by shiki and shown as the browser's own text instead of inside a Monaco editor. A detail page renders each file — and a comparison page each of its two sides — as plain text with line numbers that are not copied, so the browser's own find, selection, and copy reach every character, and a detail route loads about 215 KB of colouring, as the local host serves it, where it loaded about 3.1 MB of editor before. A comparison keeps its two sides opposite each other at every width, marks each added or removed line with + or - beside its number as well as with colour, and highlights the words a changed line differs in. The package ships no editor worker, icon font, or WebAssembly.

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 09 Sep 00:45
c9b5537

Minor Changes

  • #9 2ae92aa Thanks @ota-meshi! - Every customization detail page is now drawn inside one frame that holds the page's own outermost element, the header above its content, the region a screen reader hears its state through, and where keyboard focus lands on arrival. Nothing looks, sounds, or answers the keyboard differently from the previous release.

  • #9 2ae92aa Thanks @ota-meshi! - A plugin detail page no longer announces "Plugin ready." when it finishes loading. Every kind is silent on arrival, as the other ten already were: focus is already on the page's heading, which has named the subject, and the session has already been announced as ready — a second "ready" says only that something changed, not what it changed into.

    A skill detail page reached by a link whose file its directory no longer holds now announces that, rather than announcing that nothing sits at the link's path. The screen has drawn those as two different states all along; a reader who cannot see it was told the skill itself was gone.

  • #9 2ae92aa Thanks @ota-meshi! - Every sentence this product shows now spells its apostrophe the same way, wherever the sentence is written. A page's own words and the words its live region speaks were the same sentence in two spellings, so the same statement reached a reader who could see the page and a reader who could not as two different strings.

  • #9 2ae92aa Thanks @ota-meshi! - A detail page's trail ends at the kind whenever it has nothing to name after it — a link this scan holds no file at, a skill whose directory it holds no row for — instead of closing on a separator with nothing behind it. Every kind reads that way; only skills did before, and the page itself already says the link is not in this scan.

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 07 Sep 22:49
ad20d20

Patch Changes

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 07 Sep 07:48
14a029e

Minor Changes

  • #5 6275375 Thanks @ota-meshi! - A plugin detail page opened at a link with no path drew an empty heading. It now names the kind, the way every other detail page does when its link names no path.

  • #5 6275375 Thanks @ota-meshi! - The outcomes a permission policy reports about declared permissions it could not read, and the ones a plugin's carrier reports, are now marked by severity the way every other page marks them: an error takes the leading edge a failure gets, anything else the weight of a note.

  • #5 6275375 Thanks @ota-meshi! - The detail pages for all eleven customization kinds now share their common headings, breadcrumbs, file facts, source-root notes, diagnostics, focus handling, and loading and failure announcements. Pages with parsed and source views also share their tab behavior, so the same navigation and status patterns stay consistent across customization kinds.

  • #6 1e44168 Thanks @ota-meshi! - The tab strip on a plugin comparison now uses the same shared presentation and behavior as detail pages with parsed and source views. Nothing looks, sounds, or answers the keyboard differently from the previous release.

  • #5 6275375 Thanks @ota-meshi! - Spacing is now the same across the pages that share a shape. The space above and below a heading, and between a heading and the link beside it, no longer differs from one customization kind to the next. And where two sections meet, each section's own spacing applies rather than the larger of the two winning, so a few gaps on the Repository page and in the disable interlude are slightly wider.

  • #3 7496f35 Thanks @ota-meshi! - Read-only source diffs for skills, instructions, prompts and commands, custom agents, and plugins now render through one shared component. Comparison behavior is unchanged.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 05 Sep 07:26
dfbd591

Minor Changes