JetBrains already writes good HTML: code inspections as reports, test plans, refactoring proposals and module overviews. The hard part is what happens next. A file on your laptop doesn't open properly on a phone, and feedback ends up in a chat thread that JetBrains never sees.
tossithere fixes that. JetBrains runs one command, and the HTML is live at a private link that opens anywhere. People comment on the exact element or sentence they mean, and JetBrains reads every comment, fixes the page and publishes v2 on the same link.
Set it up
You do this once, in Junie and the AI Assistant in JetBrains IDEs.
- Install the CLI and sign in:
npm install -g tossithere
toss login
- Install the tossithere skill. Ask JetBrains:
Install the tossithere skill from https://tossithere.com/skill.md and use it whenever you make HTML for me.
Prefer to keep it in the repository? Copy the instructions from this page instead. Paste the instructions into .junie/guidelines.md in your project. Junie reads its guidelines before every task.
That's it. JetBrains now knows how to publish, share, read comments and push new versions.
Publish your first page
Ask JetBrains for something you'd normally get as a wall of text:
Write a test plan for the billing module as an HTML page and publish it for review.
JetBrains writes the HTML and publishes it:
toss docs:push billing-test-plan.html --json
# -> https://tossithere.com/d/billing-test-plan-8fa2
The page is private to you. Open it on your laptop or your phone.
Share it and collect comments
When someone else should see it, ask JetBrains to share it, or publish straight into a team workspace:
toss docs:share <docId> --visibility public --allow comment
toss docs:push billing-test-plan.html --team <slug>
Reading needs no account. Commenting takes a Google sign-in, so every comment has a name on it. Reviewers click any element or highlight any text and type.
Let JetBrains fix it
Tell JetBrains: "Read the comments and fix the page." It runs:
toss comments:list <docId> --unresolved --json
toss docs:push billing-test-plan.html --id <docId> --note "what changed"
Every comment arrives with the exact markup it points at, so JetBrains edits the right line instead of guessing. The new version goes to the same link, and older versions stay readable with their own comments.
Tips for JetBrains
- Junie runs commands in the IDE's terminal, so it can install and use the CLI itself.
- Commit the guidelines file so the whole team's Junie publishes the same way.
- Open the link in your browser next to the IDE while you read the comments.