Repository navigation
Connect the Blog and Notes apps to the commands that drive them - #331
Conversation
The agent guide gains a Blog posts section: a post is a room note, an article never goes in a chat message, publishing is an owner's step in the Blog app, and an import should skip titles already there. rooms show prints a hint under Notes and Blog, the notes help names the apps built on it, and apps run with no action says plainly when an app names none. Closes #330 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QNDeh8UnNXHotbcjuA9MbM
Vycari ReviewRound 1 on 473070b. The verdict is the Vycari Review check run, and each open finding is an inline thread. Reply on every P0 and P1 thread: Open: P0 0 · P1 0 · P2 0 · disputed 0 · confirmed fixed 0 · withdrawn 0 Hand-off: Greptile requested on 473070b. No open findings this round. P2s, judge's notes and closed findingsJudge's notes All 2 candidate findings were refuted. |
|
@greptileai review |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QNDeh8UnNXHotbcjuA9MbM
|
@greptileai review |
Requested by Allen · project thread
Human overview
A session copying a blog into a room posted the first article as a chat message, because nothing in the help said that a blog post is a room note. This adds a Blog section to
pepper agents guide, a hint under Notes and Blog inpepper rooms show, a line in thenoteshelp, a plainer message frompepper apps run <app>when the app names no actions, and a Blog entry inhelp/cli.md. Closes #330.AI reviewer
Details for agents: what the diff does, invariants, verification, checklist
data/agent-skill/SKILL.md: new### Blog postssubsection at the end of section 8. It says a post is a room note (name = title, body = Markdown with no frontmatter or title heading), an article never goes in a chat message, an agent drafts by editing a note a member made (it cannot create one, section 9), publishing/withdrawing/listing posts is an owner's step in the Blog app with no CLI command, that publishing a note again updates its post, and that an import should list the room's notes first because creating a note never dedupes by name. It also says a post's date is the day it is published. The drift guard requires that outside section 9 the document present no command an agent token can't run, so note creation andapps runare described in prose there, not as invocations.render.py:APP_HINTS, keyed by app key, printed dim under an installed app inrooms show. Onlynotesandbloghave hints. Apps without an entry print nothing extra.cli.py: thenoteshelp names the Notes and Blog apps.apps run SLUGwith no action now prints the "owner-scoped only" note only when the list is non-empty, and a "names no actions, don't guess" line when it is empty. The--jsonoutput is unchanged.help/cli.md: a Blog posts bullet, inside<!-- rollout: blog -->so the public docs leave it out while the feature is gated.Verification:
uv run pytest -q -n autopassed with 3533 passed and 2 skipped (run before thehelp/cli.mdedit, which is Markdown only). After that edit,tests/test_docs_push.pypassed with 9 tests, andruff format --check,ruff checkandty check src/pepper_cli/were clean.Checklist (repo-specific)
uv run ruff format --checkanduv run ruff checkclean (no new lint ignores)uv run ty check src/pepper_cli/cleanuv run pytestpasses; coverage floor in.claude/maintainerd.jsonnot loweredSKILL.mdupdated if commands or output changedhelp/cli.mdupdatedGenerated by Claude Code


Confidence Score: 5/5
The PR appears safe to merge; the previous help issue is fixed and no new actionable issues were found.Summary
The PR explains that Blog posts start as room notes and that owners publish them in the Blog app.
Reviews (2) · Last reviewed commit: "Show the notes help in pepper notes --he..." · Reviewed by Greptile