Skip to content

feat: Add notes-to-action-items template#184

Open
Havishh-k wants to merge 1 commit into
Lamatic:mainfrom
Havishh-k:agentkit-challenge-notes
Open

feat: Add notes-to-action-items template#184
Havishh-k wants to merge 1 commit into
Lamatic:mainfrom
Havishh-k:agentkit-challenge-notes

Conversation

@Havishh-k

@Havishh-k Havishh-k commented Jul 7, 2026

Copy link
Copy Markdown

1. Select Contribution Type

  • Kit (kits/<category>/<kit-name>/)
  • Bundle (bundles/<bundle-name>/)
  • Template (Located in kits/notes-to-action-items/ per the new CONTRIBUTING.md flat structure guidelines)

2. General Requirements

  • PR is for one project only (no unrelated changes)
  • No secrets, API keys, or real credentials are committed
  • Folder name uses kebab-case and matches the flow ID
  • All changes are documented in README.md (purpose, setup, usage)

3. File Structure (Check what applies)

  • lamatic.config.ts (new format replacing config.json) present with valid metadata (name, description, tags, steps, author, env keys)
  • All flows in flows/<flow-name>/ (where applicable) include:
    • Flow exported in new .ts format via Lamatic Studio export standard
    • Prompts, constitutions, and model-configs properly extracted
    • README.md and agent.md
  • .env.example with placeholder values only (kits only) - N/A for template
  • No hand‑edited flow config.json node graphs (changes via Lamatic Studio export)

4. Validation

  • npm install && npm run dev works locally (kits: UI runs; bundles/templates: flows are valid)
  • PR title is clear (feat: Add notes-to-action-items template as per new guidelines)
  • GitHub Actions workflows pass (all checks are green)
  • All CodeRabbit or other PR review comments are addressed and resolved
  • No unrelated files or projects are modified

Description of changes

Added a new notes-to-action-items template 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 .ts export format outlined in the updated CONTRIBUTING.md.)

  • Added a new kits/notes-to-action-items/ template for turning messy meeting notes into structured action items with an LLM.
  • Added lamatic.config.ts in the new flat template format, defining the kit metadata and a single required notes-to-action-items step.
  • Added the main flow definition in flows/notes-to-action-items.ts:
    • trigger node
    • LLM dynamic generation node
    • API response node
    • edges wiring trigger → LLM → response, plus trigger → response
  • Added prompt assets for the flow:
    • system prompt to extract actionable tasks from raw notes
    • user prompt that injects {{triggerNode_1.output.notes}}
  • Added a model config file for the generate-text step.
  • Added a default constitution with guardrails against harmful/illegal/discriminatory output and fabricated action items.
  • Added documentation files:
    • README.md with setup and usage overview
    • agent.md describing the agent/template purpose
  • Added .gitignore entries for node_modules, .env files, and .DS_Store.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

:robot_face: AgentKit Structural Validation

New Contributions Detected

  • Template: kits/notes-to-action-items

Check Results

Check Status
No edits to existing kits ✅ Pass
Required root files present ✅ Pass
Flow .ts files present ✅ Pass
lamatic.config.ts valid ✅ Pass
No changes outside kits/ ✅ Pass

🎉 All checks passed! This contribution follows the AgentKit structure.

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

This 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.

Changes

Notes to Action Items Kit

Layer / File(s) Summary
Flow definition: meta, inputs, references, nodes, edges
kits/notes-to-action-items/flows/notes-to-action-items.ts
Defines flow metadata, empty inputs, references to constitution/prompts/model configs, a trigger→LLM→API response node graph, connecting edges, and a default export bundling all pieces.
Model config and prompt templates
kits/notes-to-action-items/model-configs/notes-to-action-items_generate-text.ts, kits/notes-to-action-items/prompts/*
Adds the generative model config plus system prompt instructing extraction of tasks/assignees/deadlines and a user prompt interpolating trigger node notes.
Kit configuration, constitution, and documentation
kits/notes-to-action-items/lamatic.config.ts, kits/notes-to-action-items/constitutions/default.md, kits/notes-to-action-items/README.md, kits/notes-to-action-items/agent.md, kits/notes-to-action-items/.gitignore
Adds the Lamatic template config, default constitution rules constraining generated content, README/agent.md documentation of the kit's purpose and flow, and .gitignore entries.

Suggested reviewers: amanintech, d-pamneja

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)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly states the new notes-to-action-items template and matches the main change set.
Description check ✅ Passed The description covers the template checklist, validation, structure notes, and a clear summary of the added template.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 win

Same 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

📥 Commits

Reviewing files that changed from the base of the PR and between dafde4c and a411ce9.

📒 Files selected for processing (9)
  • kits/notes-to-action-items/.gitignore
  • kits/notes-to-action-items/README.md
  • kits/notes-to-action-items/agent.md
  • kits/notes-to-action-items/constitutions/default.md
  • kits/notes-to-action-items/flows/notes-to-action-items.ts
  • kits/notes-to-action-items/lamatic.config.ts
  • kits/notes-to-action-items/model-configs/notes-to-action-items_generate-text.ts
  • kits/notes-to-action-items/prompts/notes-to-action-items_generate-text_system.md
  • kits/notes-to-action-items/prompts/notes-to-action-items_generate-text_user.md

Comment on lines +1 to +5
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"
};

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 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.

Suggested change
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

@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

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:

  1. Read through all CodeRabbit comments carefully
  2. Address each issue raised (or reply explaining why you disagree)
  3. Push your fixes as new commits
  4. Once all issues are resolved, comment here so we can re-review

This helps keep the review process efficient for everyone. Thank you! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant