MarkLoop

markloop is a local CLI plus browser UI for reviewing Markdown in iterative rounds.

Install

npm install -g markloop

Usage

Create a review task from a Markdown file:

markloop create path/to/file.md

Create a review task from stdin:

printf '%s' "$MARKDOWN" | markloop create

Read annotations for an existing task:

markloop get <taskId>

Start another review round from an existing task:

markloop update <taskId> path/to/file.md

Configure the host used in generated review URLs:

markloop set host your-machine.tailnet.ts.net

Start the local MarkLoop server:

markloop serve [port]

Release flow

This repository publishes the markloop package to npm from GitHub Actions when a Git tag matching v*.*.* is pushed.

1. Update package.json to the target version.
2. Commit the release change.
3. Create a matching tag, for example v0.1.0.
4. Push the commit and tag to GitHub.
5. GitHub Actions runs .github/workflows/publish.yml, verifies the tag matches package.json, runs npm ci, npm test, npm run build, npm pack --dry-run, and then publishes the package.

npm publish permissions

The workflow currently publishes with an npm token stored as a GitHub repository secret named NPM_TOKEN.

For the first release:

1. Create an npm token that is allowed to publish packages.
2. Add it to the GitHub repository as the NPM_TOKEN Actions secret.
3. Push a matching release tag such as v0.1.0.

This repository currently publishes with an npm token and without provenance because npm only accepts GitHub Actions provenance from public source repositories.

If you later make the repository public, you can re-enable provenance or migrate to npm trusted publishing for better security:

• GitHub organization or user: parkgogogo
• Repository: web-reviewer
• Workflow filename: publish.yml

The workflow file already lives at .github/workflows/publish.yml.

Trusted publishing is a good follow-up hardening step, but npm only allows configuring it for packages that already exist in the registry.