feat: Add notes-to-action-items template#184
Conversation
:robot_face: AgentKit Structural ValidationNew Contributions Detected
Check Results
🎉 All checks passed! This contribution follows the AgentKit structure. |
WalkthroughThis PR adds a new "Notes to Action Items" AgentKit template under kits/notes-to-action-items, including a flow definition (trigger, LLM, API response nodes/edges), model config, system/user prompts, a default constitution, lamatic.config.ts, README, agent.md, and .gitignore. ChangesNotes to Action Items Kit
Suggested reviewers: Good evening. Your mission, should you choose to accept it: review a new kit that turns chaotic meeting notes into crisp action items — trigger, LLM, response, no explosions required. This message will self-destruct once merged. Good luck. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
kits/notes-to-action-items/flows/notes-to-action-items.ts (1)
66-68: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winSame circular reference propagates here — this node will inherit the broken config.
This mirrors the self-referential values in
notes-to-action-items_generate-text.ts; fixing the root cause there resolves this automatically.🤖 Prompt for 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. In `@kits/notes-to-action-items/flows/notes-to-action-items.ts` around lines 66 - 68, The config entries in notes-to-action-items are still pointing back to the same generated model config, so this node will inherit the circular reference from notes-to-action-items_generate-text.ts. Update the notes-to-action-items flow to reference the correct upstream config or source values instead of the self-referential `@model-configs/notes-to-action-items_generate-text.ts` path, and verify the symbols memories, messages, and generativeModelName are all aligned with the fixed root config.
🤖 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/notes-to-action-items/model-configs/notes-to-action-items_generate-text.ts`:
- Around line 1-5: The default export in notes-to-action-items_generate-text is
self-referential, so replace the circular references for generativeModelName,
memories, and messages with real config values. Update the exported object to
point generativeModelName at an actual model identifier, and set memories and
messages to their respective concrete config structures instead of this same
module. Use the existing notes-to-action-items_generate-text export shape as the
location to swap in valid model config data so the downstream LLM node can
resolve it correctly.
---
Duplicate comments:
In `@kits/notes-to-action-items/flows/notes-to-action-items.ts`:
- Around line 66-68: The config entries in notes-to-action-items are still
pointing back to the same generated model config, so this node will inherit the
circular reference from notes-to-action-items_generate-text.ts. Update the
notes-to-action-items flow to reference the correct upstream config or source
values instead of the self-referential
`@model-configs/notes-to-action-items_generate-text.ts` path, and verify the
symbols memories, messages, and generativeModelName are all aligned with the
fixed root config.
🪄 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: cd9686e5-a265-4c10-bd14-2f32be587e48
📒 Files selected for processing (9)
kits/notes-to-action-items/.gitignorekits/notes-to-action-items/README.mdkits/notes-to-action-items/agent.mdkits/notes-to-action-items/constitutions/default.mdkits/notes-to-action-items/flows/notes-to-action-items.tskits/notes-to-action-items/lamatic.config.tskits/notes-to-action-items/model-configs/notes-to-action-items_generate-text.tskits/notes-to-action-items/prompts/notes-to-action-items_generate-text_system.mdkits/notes-to-action-items/prompts/notes-to-action-items_generate-text_user.md
| export default { | ||
| "generativeModelName": "@model-configs/notes-to-action-items_generate-text.ts", | ||
| "memories": "@model-configs/notes-to-action-items_generate-text.ts", | ||
| "messages": "@model-configs/notes-to-action-items_generate-text.ts" | ||
| }; |
There was a problem hiding this comment.
🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win
Your mission, should you choose to accept it: replace this circular self-reference with an actual model config.
generativeModelName, memories, and messages all point back to notes-to-action-items_generate-text.ts itself — a self-referential loop instead of real values (e.g. a model identifier string, a memory config object, a message template array). As written, resolving these fields at runtime will either error out or silently no-op, breaking the LLM node downstream.
🕵️ Proposed fix — populate with real values
export default {
- "generativeModelName": "`@model-configs/notes-to-action-items_generate-text.ts`",
- "memories": "`@model-configs/notes-to-action-items_generate-text.ts`",
- "messages": "`@model-configs/notes-to-action-items_generate-text.ts`"
+ "generativeModelName": "openai/gpt-4o-mini",
+ "memories": [],
+ "messages": []
};📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| export default { | |
| "generativeModelName": "@model-configs/notes-to-action-items_generate-text.ts", | |
| "memories": "@model-configs/notes-to-action-items_generate-text.ts", | |
| "messages": "@model-configs/notes-to-action-items_generate-text.ts" | |
| }; | |
| export default { | |
| "generativeModelName": "openai/gpt-4o-mini", | |
| "memories": [], | |
| "messages": [] | |
| }; |
🤖 Prompt for 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.
In
`@kits/notes-to-action-items/model-configs/notes-to-action-items_generate-text.ts`
around lines 1 - 5, The default export in notes-to-action-items_generate-text is
self-referential, so replace the circular references for generativeModelName,
memories, and messages with real config values. Update the exported object to
point generativeModelName at an actual model identifier, and set memories and
messages to their respective concrete config structures instead of this same
module. Use the existing notes-to-action-items_generate-text export shape as the
location to swap in valid model config data so the downstream LLM node can
resolve it correctly.
Source: Coding guidelines
|
Hi @Havishh-k! 👋 Before this PR can be reviewed by maintainers, please resolve all comments and requested changes from the CodeRabbit automated review. Steps to follow:
This helps keep the review process efficient for everyone. Thank you! 🙏 |
1. Select Contribution Type
kits/<category>/<kit-name>/)bundles/<bundle-name>/)kits/notes-to-action-items/per the newCONTRIBUTING.mdflat structure guidelines)2. General Requirements
kebab-caseand matches the flow IDREADME.md(purpose, setup, usage)3. File Structure (Check what applies)
lamatic.config.ts(new format replacingconfig.json) present with valid metadata (name, description, tags, steps, author, env keys)flows/<flow-name>/(where applicable) include:.tsformat via Lamatic Studio export standardREADME.mdandagent.md.env.examplewith placeholder values only (kits only) - N/A for templateconfig.jsonnode graphs (changes via Lamatic Studio export)4. Validation
npm install && npm run devworks locally (kits: UI runs; bundles/templates: flows are valid)feat: Add notes-to-action-items templateas per new guidelines)Description of changes
Added a new
notes-to-action-itemstemplate that solves the problem of organizing messy meeting notes by turning them into clean, structured action items using an LLM.This addresses the AgentKit Challenge by implementing a focused, practical single-flow API pipeline.
(Note to reviewers: I followed the new flat directory structure and
.tsexport format outlined in the updatedCONTRIBUTING.md.)kits/notes-to-action-items/template for turning messy meeting notes into structured action items with an LLM.lamatic.config.tsin the new flat template format, defining the kit metadata and a single requirednotes-to-action-itemsstep.flows/notes-to-action-items.ts:{{triggerNode_1.output.notes}}README.mdwith setup and usage overviewagent.mddescribing the agent/template purpose.gitignoreentries fornode_modules,.envfiles, and.DS_Store.