apply-comments

Applies @slide-comment JSX markers to update slide source files.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill apply-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-comments
Source: https://github.com/compozy/agh/tree/main/packages/slides/.agents/skills/apply-comments
Command: npx skills add https://github.com/compozy/agh --skill apply-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes editor-created @slide-comment markers by turning the requested notes into concrete changes inside the corresponding slide source files.

Core Features & Use Cases

  • Marker-driven slide edits: Detects and processes {@/* @slide-comment ... */} JSX markers embedded in slides/<slideId>/index.tsx.
  • Context-aware updates: Locates the enclosing JSX target for each marker and applies edits in a way that stays consistent with the slide-authoring structure.
  • Safe, verifiable workflow: Applies edits from bottom to top to avoid line-shift issues, deletes each marker after applying its change, and verifies that no markers remain.
  • Use Case: When the open-slide inspector has flagged multiple elements with notes like “make this red” or “change the accent text,” this Skill updates the slide code and cleans up the markers so the slide renders correctly.

Quick Start

Use apply-comments to process the pending inspector markers in the specified slide files under slides/ (for example, ask it to apply comments for a given slide id or for all slides).

Frequently Asked Questions about apply-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply pending slide comments to update JSX source files?

To apply pending slide comments, the Skill detects JSX marker comments in your slide source files, decodes their base64url JSON payloads, and updates the corresponding target elements to reflect the requested UI edits.

What is the safest way to batch process inspector comments across all slides?

The safest way to batch process inspector comments is applying edits in reverse line-order from bottom to top, which prevents line-shift issues while updating multiple slides and deleting markers after each change.

Why do my slide code edits shift lines when applying multiple inspector comments?

Slide code edits shift lines when markers are applied top-to-bottom because earlier edits alter subsequent line numbers, so applying edits in reverse line-order from bottom to top ensures each line reference stays valid.

Can I use this to resolve inspector notes within a React slide authoring structure?

Yes, you can use this to resolve inspector notes by locating the enclosing JSX target element for each marker and applying context-aware updates that maintain consistency with your React slide authoring structure.

How do I verify that all slide comment markers have been successfully removed?

To verify all slide comment markers are removed, the Skill performs a post-edit verification step using exact regex detection to ensure zero remaining markers exist in the updated slide source code.