Release RPG-Kit CLI.#53
Merged
Merged
Conversation
Highlight the RPG-Kit open-source update and include a graph visualization snapshot so readers can discover the generated RPG view. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Reframe positioning: RPG-ZeroRepo as an ecosystem of four components (RPG-Kit, ZeroRepo, RPG-Encoder, RepoCraft) connected by a single RPG-centered loop - New System Overview with forward/reverse loop diagram and dogfooded RPG visualization (rpgkit_visualized_graph.jpg) - New "Which component should I use?" table and "Why RPG for long-horizon coding?" problem/solution table - Quick Start split by task: A) RPG-Kit, B) ZeroRepo standalone, C) RPG-Encoder standalone - News reordered: RPG-Kit launch + RPG-Encoder ICML 2026 acceptance at top; older release-process and arXiv-duplicate items pruned - Move ZeroRepo Phase 1/2/3 internals (skeleton design, interface design, task planning, TDD loop, checkpoint format, intermediate files, configuration) to docs/zerorepo-pipeline.md - Add ICML 2026 badge for RPG-Encoder paper Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The "Direction" column forced RPG-Kit into a one-way pipeline framing that did not fit (RPG-Kit is a plug-in, not a pipeline). The new "Type" column labels each component directly: - RPG-Kit: Agent plug-in / toolkit - ZeroRepo: RPG paper code - RPG-Encoder: RPG-Encoder paper code - RepoCraft: Benchmark This makes the audience match immediate — practitioners look at the toolkit row, researchers look at the paper-code rows. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The previous section had three abstract flow diagrams but did not tell the reader which components to use for each scenario. Rewrite into three concrete scenarios with explicit component mapping: 1. Generate from scratch -> RPG (ZeroRepo) only 2. Understand existing repo -> RPG-Encoder only 3. Plan and apply non-trivial changes -> Encoder + RPG planning, the closed loop. This is what /rpgkit.rpg_edit is built for. Each scenario now lists components used and concrete entry points (both standalone and through RPG-Kit) for readers to act on. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Per second review pass: - Workflow table: rename "Why it helps" to "Benefit"; tighten row text (drop redundancies in scenarios and benefit cells) - Bridge sentence: "guide" -> "drive", add "graph-aware" before "updates" to keep RPG-driven framing consistent - RPG-Kit bullet list: add "update code and RPG together so the graph stays aligned with the repository" to surface the complex-update capability (scenario 3) as a first-class feature Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The single flat workflow table mixed agent-facing scenarios (RPG-Kit usage) with standalone research pipelines, forcing readers to mentally sort which rows applied to which audience. Split into two grouped sub-tables under the same heading: - "Inside a coding agent — use RPG-Kit": four scenarios (understand, generate, update, navigate) that RPG-Kit handles end-to-end. - "Standalone — use the research code or benchmark directly": three scenarios for ZeroRepo, RPG-Encoder, and RepoCraft when used without an agent. Bridge paragraph moved above both tables to set up the split. The "What is each component?" component-map table is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Hero: add pain sentence (agents lose repo-level context) so the reader sees the why before the what, then introduce RPG-Kit as the persistent RPG workspace solution - Move "Why RPG for long-horizon coding?" up to right after News and rewrite as "Why RPG-Kit?" with a Without/With table framed in user-facing terms (chat-history vs structured RPG, drift vs connected graph, local edits vs impact analysis, etc.) - RPG-Kit section bullets: switch from user-task bullets (which duplicated the workflow table) to interface bullets (CLI / slash commands / MCP tools) - "What can I do?" table: rename last column to "Benefit"; first row "Plan an RPG" -> "Create an RPG plan" for readability - Move "Standalone research code" below the RPG-Kit section so the upper half is fully kit-focused - Rename "RPG ecosystem overview" -> "How RPG-Kit relates to the research code" and shrink it to a short two-line pseudocode plus one sentence (the big ASCII loop is no longer needed once the RPG-Kit workspace diagram is present) - Soften the post-commit hook claim from "stays current either way" to "can be reflected back into the graph" - Copy: "this very repository" -> "this repository"; "The research code is also included" -> "The repository also includes the research code" Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Collapse Why RPG-Kit?, What can I do, Quick Start, and the RPG-Kit details into a single ## RPG-Kit parent section with ### subheadings - Collapse ZeroRepo, RPG-Encoder, RepoCraft into ### subheadings under a single ## Standalone research code parent (with intro absorbing the former "How RPG-Kit relates to the research code") - Drop the RPG-Kit Overview ASCII workspace diagram; the intro paragraph plus the three-interface bullets already convey the same picture without taking up the section - Move ## Documentation from the bottom to right after ## News so readers can find sub-docs without scrolling to the end Top-level headings now: News, Documentation, RPG-Kit, Standalone research code, Papers, Acknowledgements, License. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The opening previously framed RPG-Kit as a tool to "make AI coding agents understand the whole repository". That covers only one of the three workflows (Understand) and reads more like a context/memory enhancer than a planning layer. Updated to match the main README's positioning: RPG-Kit is the persistent RPG workspace that lets agents plan before they edit. Specific changes: - Heading: "Make AI coding agents understand the whole repository" -> "Make coding agents plan before they edit" - Opening paragraphs rewritten to describe planning failure modes (drift, inconsistency, missed dependencies) and the persistent RPG workspace solution - Add a three-bullet Build / Understand / Update list to mirror the main README's workflow framing - Choose your workflow table: rename Forward / Reverse / Surgical to Build / Understand / Update; keep the data-flow shape in parentheses - Update workflow row: add "edit plan" stage to better reflect the graph-aware edit pipeline Polish: - Fold the large workflow-details ASCII diagram into a <details> block titled "Detailed pipeline" with a "new users can skip" note, so the opening is not overwhelmed by the engineering diagram - Add a "RPG-Kit in action" heading before the graph visualization - Use the canonical .rpgkit/data/rpg.html path in the caption - Rewrite the awkward "the workspace keeps unchanged" sentence to a clear statement that rpgkit init does not modify source files - "✅(No MCP)" -> "✅ (No MCP)" spacing - Upcoming features: "Simpler decoder commands" -> "Simpler generation commands" to drop internal jargon Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bonytu
approved these changes
May 15, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the initial RPG-Kit package for repository-level planning, graph encoding, and AI-agent-assisted code generation/editing workflows.
rpgkitCLI package with init, update, check, version, MCP, hook, and workflow support