agentsclimarketplace

Openpress apply comments

Skill quan0715/open-press/skills/openpress-apply-comments

AI-first fixed-layout document workspaces. Your AI agent writes proposals, whitepapers, theses, books — A4, PDF, web reader.

Install
npx -y skills add quan0715/open-press --skill openpress-apply-comments

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when applying, resolving, clearing, or inspecting pending open-press @openpress-comment markers, including requests like /apply-comments, apply comment, resolve comments, read comments and modify the document, or remove resolved comment markers.

SKILL.md

3.6 KB, as published. Nobody here has run it

open-press Apply Comments

This is the workflow skill for turning pending @openpress-comment markers into source edits. A comment is resolved only when the requested source change has been made and the marker has been removed.

Responsibilities

  • List pending @openpress-comment markers.
  • Read the decoded comment note, hint, source path, and nearby source.
  • Apply the requested edit as a small source change.
  • Remove the marker after the edit is complete.
  • Leave ambiguous or failed comments in place.
  • Verify before reporting completion.

Boundary

  • Use openpress for the canonical source/generated path table when unsure.
  • Edit source, not generated output.
  • Default to editing the source file that contains the marker.
  • Route domain-heavy work to the owning skill:
    • openpress-create-pages for page prose, hierarchy, captions, claims, tone, narrative, page theme, and page components.
    • openpress-create-slide for deck narrative, slide density, slide-style templates, theme tokens, core Object API composition, Tailwind semantic styling, and reusable UI primitives.
    • openpress-diagram-drawing for diagram semantics.
  • Do not rewrite unrelated sections while resolving one comment.

Workflow

  1. Discover comments.

    rg "@openpress-comment" press -n

    If decoded notes are needed and the framework helper exists, use it:

    node --input-type=module -e 'import { listCommentMarkers } from "./packages/core/engine/react/comment-marker.mjs"; console.log(JSON.stringify(await listCommentMarkers({ root: process.cwd() }), null, 2));'

  2. Pick the requested scope.

    • If the user names one comment, resolve only that comment.
    • If the user says apply comments without an id, process pending comments in source order.
    • Handle comments one at a time; do not batch unrelated rewrites under one marker.

  3. Inspect the target.

    • Read the source file that contains the marker.
    • Inspect nearby lines before editing.
    • Use the marker hint and rendered-object metadata when present, but verify against source.

  4. Apply the edit.

    • Make the smallest source change that satisfies the comment.
    • Preserve local style, component APIs, and MDX structure.
    • If the request is ambiguous, ask for clarification and leave the marker in place.

  5. Remove the resolved marker.

    • Delete the @openpress-comment marker only after the source edit is complete.
    • Do not clear a marker just because it was read.
    • Clear a marker without applying only when the user explicitly asks.

  6. Verify.

    npm run build

    build validates structure and renders the full output. When iterating fast on the inner steps:

    node engine/cli.mjs validate .   # structural checks only, no render
node engine/cli.mjs export .     # rewrite document.json only, no Vite bundle

Completion Report

Report:

  • which comment ids were resolved,
  • which files changed,
  • which comments remain because they were ambiguous or failed,
  • which verification commands ran and whether they passed.

Common Mistakes

  • Do not edit public/openpress/, dist-react/, .deploy/, or .openpress/.
  • Do not remove unresolved comments.
  • Do not rewrite broad sections unless the comment explicitly asks for that.
  • Do not claim the browser changed until the source has been exported when export is required.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.