feat: [kit] Add paper-to-project generator#175
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (10)
WalkthroughAdds a new Lamatic kit that converts research papers into actionable project roadmaps via a chained workflow: paper analysis → roadmap generation → project planning → markdown report, including prompts, model configs, constitution, flow definition, kit metadata, and documentation. ChangesPaper-to-Project Generator Kit
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Author
|
@coderabbitai review |
Contributor
✅ Action performedReview finished.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/paper-to-project/agent.md`:
- Line 21: The file ends without a trailing newline which triggers MD047; add a
single newline character at the end of the file so the final line "Professional
markdown report" is terminated with one trailing newline.
In
`@kits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-606_system_0.md`:
- Around line 3-11: The system prompt currently directs extraction of 7 fields
but must require all 9 keys defined by the InstructorLLMNode_606 schema; update
the prompt text in
research-to-project-planner_instructor-llmnode-606_system_0.md to explicitly
list and require extraction for every InstructorLLMNode_606 schema field
(mentioning the schema name InstructorLLMNode_606 to locate it), ensure
instructions state "Provide all 9 schema keys" and enumerate them verbatim in
the prompt, and enforce that values are precise, factual, and only drawn from
the paper so downstream nodes receive a complete, stable structured payload.
In
`@kits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-606_user_1.md`:
- Around line 3-11: The prompt in
kits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-606_user_1.md
currently asks for a 7-field extraction but the downstream schema
InstructorLLMNode_606 requires a full 9-field JSON; update the prompt text to
explicitly request the exact nine keys required by InstructorLLMNode_606 (list
each key name in order so the model returns a deterministic JSON with those
keys) and change the instruction "Return the information in the required JSON
structure." to explicitly state "Return a JSON object with these nine keys:
<enumerate the nine schema keys exactly>" so the extractor always emits the
complete 9-field payload matching the InstructorLLMNode_606 schema.
In
`@kits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-728_user_1.md`:
- Line 9: The prompt contains a single concatenated instruction token that
merges the five list items and "Return JSON only" into one stream, impairing
parsing; split that token into distinct list items so each appears on its own
line or as separate numbered entries (e.g., "1. Development Modules", "2.
Detailed Tasks", "3. Weekly Milestones", "4. Risks and Challenges", "5. Final
Deliverables", and a separate "Return JSON only" instruction) — update the
prompt string in research-to-project-planner_instructor-llmnode-728_user_1.md
where the concatenated instruction line appears so downstream parsers and the
planner generator functions consume each item independently.
In `@kits/paper-to-project/README.md`:
- Line 138: The README.md is missing a trailing newline which triggers MD047;
open the file and ensure it ends with a single newline character after the final
line containing "Google Gemini 2.5 Flash" (i.e., add a newline at EOF), then
save so the file ends with a terminating newline to satisfy markdownlint.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: 5b4f768b-28ee-47ff-b65c-4286ea073091
⛔ Files ignored due to path filters (3)
kits/paper-to-project/screenshots/sample-input.pngis excluded by!**/*.pngkits/paper-to-project/screenshots/sample-output.pngis excluded by!**/*.pngkits/paper-to-project/screenshots/workflow.pngis excluded by!**/*.png
📒 Files selected for processing (18)
kits/paper-to-project/.gitignorekits/paper-to-project/README.mdkits/paper-to-project/agent.mdkits/paper-to-project/constitutions/default.mdkits/paper-to-project/flows/research-to-project-planner.tskits/paper-to-project/lamatic.config.tskits/paper-to-project/model-configs/research-to-project-planner_instructor-llmnode-606_generative-model-name.tskits/paper-to-project/model-configs/research-to-project-planner_instructor-llmnode-728_generative-model-name.tskits/paper-to-project/model-configs/research-to-project-planner_instructor-llmnode-842_generative-model-name.tskits/paper-to-project/model-configs/research-to-project-planner_llmnode-959_generative-model-name.tskits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-606_system_0.mdkits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-606_user_1.mdkits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-728_system_0.mdkits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-728_user_1.mdkits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-842_system_0.mdkits/paper-to-project/prompts/research-to-project-planner_instructor-llmnode-842_user_1.mdkits/paper-to-project/prompts/research-to-project-planner_llmnode-959_system_0.mdkits/paper-to-project/prompts/research-to-project-planner_llmnode-959_user_1.md
akshatvirmani
changed the title
Contributor
:robot_face: AgentKit Structural ValidationNew Contributions Detected
Check Results
🎉 All checks passed! This contribution follows the AgentKit structure. |
Contributor
|
Failure recorded at 2026-06-06T12:34:47Z UTC. If this PR is not fixed within 4 weeks it will be automatically closed. |
Contributor
|
/validate |
Contributor
|
📡 Running Studio validation — results will appear here shortly. |
Contributor
Studio Runtime Validation (Phase 2)✅ Studio validation passed. The kit loaded successfully in Lamatic Studio. This PR is ready for final review and merge. |
Contributor
|
@ArushJ22 can you check the GitHub action above? lamatic.config.ts is failing |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@kits/paper-to-project/lamatic.config.ts`:
- Line 2: The configuration's name field uses machine-readable kebab-case
("paper-to-project") but should use the human-readable title used across docs;
update the name property in lamatic.config.ts to the user-facing title
"Paper-to-Project Generator" so it matches the established pattern and CI checks
(locate the name: "paper-to-project" entry in lamatic.config.ts and replace it
with the human-readable string).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: e5703bb2-537e-44ce-804a-82fdbae089d9
📒 Files selected for processing (1)
kits/paper-to-project/lamatic.config.ts
Contributor
|
/validate |
Contributor
|
📡 Running Studio validation — results will appear here shortly. |
Contributor
|
@ArushJ22 can you resolve the coderabbit comments above? |
Contributor
|
/validate |
Contributor
|
📡 Running Studio validation — results will appear here shortly. |
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.
Summary
Adds a new AgentKit called Paper-to-Project Generator.
This agent converts research papers into practical software project roadmaps by:
Features
Workflow
Chat Widget
→ Paper Analysis
→ Project Roadmap
→ Project Planner
→ Report Generator
→ Chat Response
Files Added
Testing
Files added
Flow: research-to-project-planner — high-level summary & node types