Open
Conversation
Contributor
WalkthroughAdds a new Medical Assistant kit: a Next.js + Tailwind frontend chat UI, Lamatic flow definitions and orchestration, Lamatic client and server action to execute queries (with polling/error handling), configuration and tooling files, UI components (disclaimer), and documentation/metadata. Changes
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 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 |
![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: 7
🧹 Nitpick comments (5)
kits/assistant/medical-assistant/package.json (1)
16-16: Consider movingautoprefixertodevDependencies.
autoprefixeris a build-time tool for PostCSS and doesn't need to be in production dependencies. Moving it todevDependenciesreduces the production bundle footprint.♻️ Proposed fix
"dependencies": { "@radix-ui/react-scroll-area": "^1.2.3", "@radix-ui/react-slot": "^1.1.1", "@tailwindcss/typography": "^0.5.19", "@vercel/analytics": "^1.5.0", - "autoprefixer": "^10.4.27", "class-variance-authority": "^0.7.1","devDependencies": { "@tailwindcss/postcss": "^4.0.6", "@types/node": "^20", "@types/react": "^19", "@types/react-dom": "^19", + "autoprefixer": "^10.4.27", "postcss": "^8.5.6",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/package.json` at line 16, The package.json currently lists "autoprefixer" in dependencies; move it to devDependencies by removing the "autoprefixer" entry from the top-level "dependencies" object and adding the same version string under "devDependencies" so it is installed only in development/build environments; update any package-lock or yarn.lock by reinstalling deps if needed to reflect the change.kits/assistant/medical-assistant/.env.example (1)
1-4: Remove spaces around equal signs in.env.example.Some
.envparsers don't handle spaces around the=sign correctly, which could lead to configuration issues. The standard convention isKEY=valuewithout spaces.♻️ Proposed fix
-MEDICAL_ASSISTANT_CHAT = "MEDICAL_ASSISTANT_CHAT Flow ID" -LAMATIC_API_URL = "LAMATIC_API_URL" -LAMATIC_PROJECT_ID = "LAMATIC_PROJECT_ID" -LAMATIC_API_KEY = "LAMATIC_API_KEY" +MEDICAL_ASSISTANT_CHAT="your_flow_id_here" +LAMATIC_API_URL="https://api.lamatic.ai" +LAMATIC_PROJECT_ID="your_project_id_here" +LAMATIC_API_KEY="your_api_key_here"Note: The proposed fix also aligns placeholder values with the README documentation format for consistency.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/.env.example` around lines 1 - 4, Remove the spaces around the equals signs in the environment variable declarations for MEDICAL_ASSISTANT_CHAT, LAMATIC_API_URL, LAMATIC_PROJECT_ID, and LAMATIC_API_KEY so each line follows KEY=value format (no surrounding spaces) and update the placeholder values to match the README's placeholder style for consistency.kits/assistant/medical-assistant/tsconfig.json (1)
11-13: Consider enabling full strict mode for better type safety.The current configuration sets
strict: falsewhile manually enablingstrictNullChecksandnoImplicitAny. This is an unusual pattern. Usingstrict: truewould enable all strict options (includingstrictBindCallApply,strictFunctionTypes,strictPropertyInitialization, etc.) for more comprehensive type checking.♻️ Proposed change
- "strict": false, - "strictNullChecks": true, - "noImplicitAny": true, + "strict": true,🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/tsconfig.json` around lines 11 - 13, The tsconfig currently has "strict": false while individually enabling "strictNullChecks" and "noImplicitAny"; change to enable full strict mode by setting "strict": true and remove or keep the individual flags for clarity (they become redundant) so that all strict checks (e.g., strictBindCallApply, strictFunctionTypes, strictPropertyInitialization) are enforced; update the JSON entry for the "strict" compiler option and ensure the "strictNullChecks" and "noImplicitAny" lines are consistent with that change.kits/assistant/medical-assistant/actions/orchestrate.ts (1)
6-14: Add server-side query guardrails (empty/oversized).Relying only on client checks is fragile. A lightweight server boundary check will reduce avoidable provider calls and failure noise.
✅ Suggested guardrails
export async function sendMedicalQuery( query: string, ): Promise<{ @@ }> { try { + const trimmedQuery = query?.trim() + if (!trimmedQuery) { + return { success: false, error: "Query cannot be empty." } + } + if (trimmedQuery.length > 2000) { + return { success: false, error: "Query is too long. Please shorten and try again." } + } - console.log("[medical-assistant] Processing query, length:", query.length) + console.log("[medical-assistant] Processing query, length:", trimmedQuery.length) @@ - query, + query: trimmedQuery,🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/actions/orchestrate.ts` around lines 6 - 14, In sendMedicalQuery add server-side guardrails: trim the incoming query and if it's empty return { success: false, error: "empty query" } without calling downstream providers; if query.length exceeds a defined MAX_QUERY_LENGTH constant (e.g., MAX_QUERY_LENGTH = 2000) log the event and return { success: false, error: "query too long" }; use the existing console/logging pattern (console.log or processLogger) to record rejected queries and ensure all early returns match the function's Promise<{success:boolean, data?:any, error?:string}> shape so no provider/client calls happen for invalid input.kits/assistant/medical-assistant/app/page.tsx (1)
416-420: Copy action should be keyboard-visible, not hover-only.The button is visually hidden unless hovered; add focus-visible styles so keyboard users can discover it.
⌨️ Accessibility tweak
- className="absolute top-2 opacity-0 group-hover:opacity-100 transition-all duration-200 p-1.5 rounded-lg" + className="absolute top-2 opacity-0 group-hover:opacity-100 focus-visible:opacity-100 focus-visible:outline focus-visible:outline-2 transition-all duration-200 p-1.5 rounded-lg"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/app/page.tsx` around lines 416 - 420, The copy control is hidden via opacity unless hovered; make it discoverable to keyboard users by adding focus/focus-visible styles and ensuring it's focusable: update the element using className (the element that currently has "absolute top-2 opacity-0 group-hover:opacity-100 ...") to include "focus-visible:opacity-100" (and/or "focus:opacity-100") and a visible focus outline class (e.g., "focus-visible:outline" or similar), and if the element is not already a native button ensure it has tabIndex={0} and keyboard handlers; keep the existing aria-label logic (aria-label={copiedId === msg.id ? "Copied" : "Copy response"}) and reference copiedId and msg.id as-is.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@kits/assistant/medical-assistant/actions/orchestrate.ts`:
- Around line 56-60: Replace raw payload logging in orchestrate.ts by removing
verbose prints of asyncResult and error; instead log only non-sensitive metadata
(e.g., requestId, status code, duration, and a redacted/summary message).
Specifically update the console.log calls around lamaticClient.checkStatus
(where requestId and asyncResult are logged) and the catch/log that prints error
to redact or stringify only safe fields (avoid user medical content or provider
internals) and add a correlation id if available; keep the detailed payloads
available only for secure debug endpoints or structured logs behind a privacy
guard.
- Around line 8-11: The returned payload currently types data as any and can
propagate non-string values; change the return type to data?: string and ensure
every assignment to data (in the orchestrate function and the parsing/return
branches around the 75-91 range) converts values to a string using a small
helper like ensureString(value) that returns '' for null/undefined, returns the
value if typeof value === 'string', otherwise returns JSON.stringify(value);
update the Promise signature from data?: any to data?: string and replace direct
data assignments with ensureString(...) to guarantee downstream UI always
receives text.
In `@kits/assistant/medical-assistant/app/globals.css`:
- Around line 3-5: Linting fails because Tailwind v4 at-rules like `@plugin` and
`@custom-variant` (and others: `@theme`, `@apply`, `@layer`, `@import`, `@tailwind`) are not
allowed by current CSS linters; update .stylelintrc.json to add these directives
to the "ignoreAtRules" list for the "at-rule-no-unknown" rule, and update
biome.json to enable Tailwind CSS parsing or disable conflicting CSS rules so
Biome's CSS linter accepts Tailwind directives; also rename the animation
identifier `@keyframes` chatMessageEnter to kebab-case `@keyframes`
chat-message-enter (and update any references to that animation) to satisfy
naming conventions.
In `@kits/assistant/medical-assistant/app/page.tsx`:
- Around line 169-247: The sidebar remains mounted and keyboard-focusable when
collapsed; change the rendering so the <aside> is only mounted when sidebarOpen
is true (e.g., wrap the aside JSX with a conditional check on the sidebarOpen
state) to remove hidden focus targets, and ensure any handlers that reference
sessions, createNewSession, setActiveSessionId, or activeSessionId still work
when the sidebar mounts/unmounts.
In `@kits/assistant/medical-assistant/flows/medical-assistant-chat/README.md`:
- Around line 23-28: The Output Schema table is malformed: the row with `query`
has four cells while the header defines three and it incorrectly documents the
input instead of the LLM response; update the table so header and all rows have
the same three columns (Field, Type, Description) and replace the `query` row
with the actual output field name from the Lamatic flow (e.g., `response` or
whatever the flow uses), its type (e.g., `string`), and a concise description of
the model's reply; verify the exact output field name in the
medical-assistant-chat flow configuration and use that identifier in the `Field`
column.
In `@kits/assistant/medical-assistant/lib/lamatic-client.ts`:
- Around line 10-19: The validation currently requires config.api.endpoint,
config.api.projectId and config.api.apiKey but lamaticClient instantiation uses
a nullable fallback for projectId; pick one behavior and make them consistent:
if projectId is required, remove the "?? null" fallback in Lamatic construction
and pass config.api.projectId (non-null) directly to new Lamatic, ensuring types
match; alternatively, if projectId should be optional, remove projectId from the
initial throw check and document/handle its absence before creating
lamaticClient (adjust the validation block and the instantiation of
lamaticClient accordingly). Reference: the validation block checking
config.api?.endpoint/config.api?.projectId/config.api?.apiKey and the exported
lamaticClient = new Lamatic({...}) lines.
In `@kits/assistant/medical-assistant/package.json`:
- Line 19: The package.json currently lists an unavailable dependency version
"lamatic": "^0.3.2"; update the dependency entry for "lamatic" to a published
version such as "lamatic": "^0.3.1" (or "0.3.1") so the dependency resolves
correctly when installing.
---
Nitpick comments:
In `@kits/assistant/medical-assistant/.env.example`:
- Around line 1-4: Remove the spaces around the equals signs in the environment
variable declarations for MEDICAL_ASSISTANT_CHAT, LAMATIC_API_URL,
LAMATIC_PROJECT_ID, and LAMATIC_API_KEY so each line follows KEY=value format
(no surrounding spaces) and update the placeholder values to match the README's
placeholder style for consistency.
In `@kits/assistant/medical-assistant/actions/orchestrate.ts`:
- Around line 6-14: In sendMedicalQuery add server-side guardrails: trim the
incoming query and if it's empty return { success: false, error: "empty query" }
without calling downstream providers; if query.length exceeds a defined
MAX_QUERY_LENGTH constant (e.g., MAX_QUERY_LENGTH = 2000) log the event and
return { success: false, error: "query too long" }; use the existing
console/logging pattern (console.log or processLogger) to record rejected
queries and ensure all early returns match the function's
Promise<{success:boolean, data?:any, error?:string}> shape so no provider/client
calls happen for invalid input.
In `@kits/assistant/medical-assistant/app/page.tsx`:
- Around line 416-420: The copy control is hidden via opacity unless hovered;
make it discoverable to keyboard users by adding focus/focus-visible styles and
ensuring it's focusable: update the element using className (the element that
currently has "absolute top-2 opacity-0 group-hover:opacity-100 ...") to include
"focus-visible:opacity-100" (and/or "focus:opacity-100") and a visible focus
outline class (e.g., "focus-visible:outline" or similar), and if the element is
not already a native button ensure it has tabIndex={0} and keyboard handlers;
keep the existing aria-label logic (aria-label={copiedId === msg.id ? "Copied" :
"Copy response"}) and reference copiedId and msg.id as-is.
In `@kits/assistant/medical-assistant/package.json`:
- Line 16: The package.json currently lists "autoprefixer" in dependencies; move
it to devDependencies by removing the "autoprefixer" entry from the top-level
"dependencies" object and adding the same version string under "devDependencies"
so it is installed only in development/build environments; update any
package-lock or yarn.lock by reinstalling deps if needed to reflect the change.
In `@kits/assistant/medical-assistant/tsconfig.json`:
- Around line 11-13: The tsconfig currently has "strict": false while
individually enabling "strictNullChecks" and "noImplicitAny"; change to enable
full strict mode by setting "strict": true and remove or keep the individual
flags for clarity (they become redundant) so that all strict checks (e.g.,
strictBindCallApply, strictFunctionTypes, strictPropertyInitialization) are
enforced; update the JSON entry for the "strict" compiler option and ensure the
"strictNullChecks" and "noImplicitAny" lines are consistent with that change.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
kits/assistant/medical-assistant/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (22)
kits/assistant/medical-assistant/.env.examplekits/assistant/medical-assistant/.gitignorekits/assistant/medical-assistant/README.mdkits/assistant/medical-assistant/actions/orchestrate.tskits/assistant/medical-assistant/app/globals.csskits/assistant/medical-assistant/app/layout.tsxkits/assistant/medical-assistant/app/page.tsxkits/assistant/medical-assistant/components.jsonkits/assistant/medical-assistant/components/disclaimer.tsxkits/assistant/medical-assistant/config.jsonkits/assistant/medical-assistant/flows/medical-assistant-chat/README.mdkits/assistant/medical-assistant/flows/medical-assistant-chat/config.jsonkits/assistant/medical-assistant/flows/medical-assistant-chat/inputs.jsonkits/assistant/medical-assistant/flows/medical-assistant-chat/meta.jsonkits/assistant/medical-assistant/lib/lamatic-client.tskits/assistant/medical-assistant/lib/utils.tskits/assistant/medical-assistant/next.config.mjskits/assistant/medical-assistant/orchestrate.jskits/assistant/medical-assistant/package.jsonkits/assistant/medical-assistant/postcss.config.cjskits/assistant/medical-assistant/tailwind.config.tskits/assistant/medical-assistant/tsconfig.json
Comment on lines
+56
to
+60
| console.log("[medical-assistant] Async response, polling with requestId:", requestId) | ||
|
|
||
| const asyncResult = await lamaticClient.checkStatus(requestId, 2, 60) | ||
| console.log("[medical-assistant] Async poll result:", asyncResult) | ||
|
|
Contributor
There was a problem hiding this comment.
Avoid logging raw workflow payloads/errors in a medical context.
Line [59] logs full asyncResult and Line [93] logs raw error. These can include user medical content or provider internals and should be sanitized.
🔒 Suggested logging hardening
- console.log("[medical-assistant] Async poll result:", asyncResult)
+ console.log("[medical-assistant] Async poll status:", asyncResult?.status)
@@
- console.error("[medical-assistant] Query error:", error)
+ const safeError =
+ error instanceof Error ? { name: error.name, message: error.message } : { message: "Unknown error" }
+ console.error("[medical-assistant] Query error:", safeError)Also applies to: 93-93
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/actions/orchestrate.ts` around lines 56 -
60, Replace raw payload logging in orchestrate.ts by removing verbose prints of
asyncResult and error; instead log only non-sensitive metadata (e.g., requestId,
status code, duration, and a redacted/summary message). Specifically update the
console.log calls around lamaticClient.checkStatus (where requestId and
asyncResult are logged) and the catch/log that prints error to redact or
stringify only safe fields (avoid user medical content or provider internals)
and add a correlation id if available; keep the detailed payloads available only
for secure debug endpoints or structured logs behind a privacy guard.
Comment on lines
+3
to
+5
| @plugin "@tailwindcss/typography"; | ||
|
|
||
| @custom-variant dark (&:is(.dark *)); |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Tailwind directives used in globals.css"
rg -n '@plugin|@custom-variant|@theme|@apply' kits/assistant/medical-assistant/app/globals.css
echo
echo "2) Lint config files"
fd -HI '(^|/)(\.stylelintrc(\..+)?|stylelint\.config\.(js|cjs|mjs|json|yaml|yml)|biome\.jsonc?|biome\.json)$' .
CONFIGS="$(fd -HI '(^|/)(\.stylelintrc(\..+)?|stylelint\.config\.(js|cjs|mjs|json|yaml|yml)|biome\.jsonc?|biome\.json)$' .)"
if [ -n "$CONFIGS" ]; then
echo
echo "3) Relevant parser/rule entries"
rg -n 'at-rule-no-unknown|ignoreAtRules|keyframes-name-pattern|tailwind|css' $CONFIGS
fiRepository: Lamatic/AgentKit
Length of output: 567
🏁 Script executed:
# Also check the full globals.css file to see the extent of the issues
wc -l kits/assistant/medical-assistant/app/globals.cssRepository: Lamatic/AgentKit
Length of output: 112
🏁 Script executed:
# Read the globals.css file to understand the full context
cat -n kits/assistant/medical-assistant/app/globals.cssRepository: Lamatic/AgentKit
Length of output: 6935
🏁 Script executed:
# Check the actual stylelint and biome configuration content
cat -n .stylelintrc.jsonRepository: Lamatic/AgentKit
Length of output: 1276
🏁 Script executed:
cat -n biome.jsonRepository: Lamatic/AgentKit
Length of output: 2345
Configure linting tools to support Tailwind v4 syntax.
Stylelint and Biome are configured but neither supports Tailwind v4 at-rules (@plugin, @custom-variant, @theme, @apply). This will cause CI failures.
Update .stylelintrc.json to allow these directives:
{
"extends": ["stylelint-config-standard-scss"],
"rules": {
"at-rule-no-unknown": [
true,
{
"ignoreAtRules": [
"plugin",
"custom-variant",
"theme",
"layer",
"apply",
"import",
"tailwind"
]
}
]
// ... existing rules
}
}Configure Biome's CSS linter for Tailwind in biome.json (lines 60-67) by adding Tailwind parser support or disabling conflicting CSS rules.
Also, rename @keyframes chatMessageEnter (line 129) to @keyframes chat-message-enter to follow kebab-case convention.
🧰 Tools
🪛 Biome (2.4.4)
[error] 3-3: Tailwind-specific syntax is disabled.
(parse)
[error] 5-5: Tailwind-specific syntax is disabled.
(parse)
🪛 Stylelint (17.3.0)
[error] 3-3: Unexpected unknown at-rule "@plugin" (scss/at-rule-no-unknown)
(scss/at-rule-no-unknown)
[error] 5-5: Unexpected unknown at-rule "@custom-variant" (scss/at-rule-no-unknown)
(scss/at-rule-no-unknown)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/app/globals.css` around lines 3 - 5, Linting
fails because Tailwind v4 at-rules like `@plugin` and `@custom-variant` (and others:
`@theme`, `@apply`, `@layer`, `@import`, `@tailwind`) are not allowed by current CSS
linters; update .stylelintrc.json to add these directives to the "ignoreAtRules"
list for the "at-rule-no-unknown" rule, and update biome.json to enable Tailwind
CSS parsing or disable conflicting CSS rules so Biome's CSS linter accepts
Tailwind directives; also rename the animation identifier `@keyframes`
chatMessageEnter to kebab-case `@keyframes` chat-message-enter (and update any
references to that animation) to satisfy naming conventions.
Comment on lines
+169
to
+247
| <aside | ||
| className={`${sidebarOpen ? "w-72" : "w-0" | ||
| } transition-all duration-300 flex flex-col overflow-hidden flex-shrink-0`} | ||
| style={{ background: '#fff', borderRight: sidebarOpen ? '1px solid #e2e8f0' : 'none' }} | ||
| > | ||
| {/* Brand */} | ||
| <div className="h-14 flex items-center gap-2 px-5 flex-shrink-0" style={{ borderBottom: '1px solid #f1f5f9' }}> | ||
| <Stethoscope className="w-5 h-5" style={{ color: '#f43f5e' }} /> | ||
| <span className="text-lg font-bold tracking-tight whitespace-nowrap"> | ||
| <span style={{ color: '#0f172a' }}>Medical</span>{" "} | ||
| <span style={{ color: '#f43f5e' }}>Assistant</span> | ||
| </span> | ||
| </div> | ||
|
|
||
| {/* New Session */} | ||
| <div className="p-3 flex-shrink-0"> | ||
| <button | ||
| onClick={createNewSession} | ||
| className="w-full flex items-center justify-center gap-2 px-4 py-2.5 rounded-xl text-sm font-medium transition-colors shadow-sm" | ||
| style={{ background: '#f43f5e', color: '#fff' }} | ||
| onMouseEnter={(e) => (e.currentTarget.style.background = '#e11d48')} | ||
| onMouseLeave={(e) => (e.currentTarget.style.background = '#f43f5e')} | ||
| > | ||
| <Plus className="w-4 h-4" /> | ||
| New Session | ||
| </button> | ||
| </div> | ||
|
|
||
| {/* Session List */} | ||
| <div className="flex-1 overflow-y-auto px-3 pb-3"> | ||
| <div className="flex flex-col gap-1"> | ||
| {sessions.length === 0 ? ( | ||
| <p className="text-center py-8 text-sm" style={{ color: '#94a3b8' }}>No sessions yet</p> | ||
| ) : ( | ||
| sessions.map((session) => ( | ||
| <button | ||
| key={session.id} | ||
| onClick={() => setActiveSessionId(session.id)} | ||
| className="w-full text-left px-3 py-2.5 rounded-lg text-sm transition-colors flex items-center gap-2.5" | ||
| style={{ | ||
| background: session.id === activeSessionId ? '#f1f5f9' : 'transparent', | ||
| color: session.id === activeSessionId ? '#0f172a' : '#475569', | ||
| fontWeight: session.id === activeSessionId ? 500 : 400, | ||
| }} | ||
| > | ||
| <MessageSquare className="w-4 h-4 flex-shrink-0" /> | ||
| <span className="truncate">{session.title}</span> | ||
| </button> | ||
| )) | ||
| )} | ||
| </div> | ||
| </div> | ||
|
|
||
| {/* Sidebar Footer Links */} | ||
| <div className="p-3 flex-shrink-0" style={{ borderTop: '1px solid #f1f5f9' }}> | ||
| <div className="flex flex-col gap-1"> | ||
| <Link | ||
| href="https://lamatic.ai/docs" | ||
| target="_blank" | ||
| rel="noopener noreferrer" | ||
| className="flex items-center gap-2 px-3 py-2 rounded-lg text-sm transition-colors" | ||
| style={{ color: '#475569' }} | ||
| > | ||
| <FileText className="w-4 h-4" style={{ color: '#94a3b8' }} /> | ||
| Documentation | ||
| </Link> | ||
| <Link | ||
| href="https://github.com/Lamatic/AgentKit" | ||
| target="_blank" | ||
| rel="noopener noreferrer" | ||
| className="flex items-center gap-2 px-3 py-2 rounded-lg text-sm transition-colors" | ||
| style={{ color: '#475569' }} | ||
| > | ||
| <Github className="w-4 h-4" style={{ color: '#94a3b8' }} /> | ||
| GitHub | ||
| </Link> | ||
| </div> | ||
| </div> | ||
| </aside> |
Contributor
There was a problem hiding this comment.
Collapsed sidebar stays in tab order while visually hidden.
When sidebarOpen is false, the sidebar content is still mounted and can remain keyboard-focusable, creating hidden focus targets.
♿ Suggested fix (render sidebar only when open)
- <aside
- className={`${sidebarOpen ? "w-72" : "w-0"
- } transition-all duration-300 flex flex-col overflow-hidden flex-shrink-0`}
- style={{ background: '#fff', borderRight: sidebarOpen ? '1px solid `#e2e8f0`' : 'none' }}
- >
+ {sidebarOpen && (
+ <aside
+ className="w-72 transition-all duration-300 flex flex-col overflow-hidden flex-shrink-0"
+ style={{ background: '#fff', borderRight: '1px solid `#e2e8f0`' }}
+ >
@@
- </aside>
+ </aside>
+ )}📝 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
| <aside | |
| className={`${sidebarOpen ? "w-72" : "w-0" | |
| } transition-all duration-300 flex flex-col overflow-hidden flex-shrink-0`} | |
| style={{ background: '#fff', borderRight: sidebarOpen ? '1px solid #e2e8f0' : 'none' }} | |
| > | |
| {/* Brand */} | |
| <div className="h-14 flex items-center gap-2 px-5 flex-shrink-0" style={{ borderBottom: '1px solid #f1f5f9' }}> | |
| <Stethoscope className="w-5 h-5" style={{ color: '#f43f5e' }} /> | |
| <span className="text-lg font-bold tracking-tight whitespace-nowrap"> | |
| <span style={{ color: '#0f172a' }}>Medical</span>{" "} | |
| <span style={{ color: '#f43f5e' }}>Assistant</span> | |
| </span> | |
| </div> | |
| {/* New Session */} | |
| <div className="p-3 flex-shrink-0"> | |
| <button | |
| onClick={createNewSession} | |
| className="w-full flex items-center justify-center gap-2 px-4 py-2.5 rounded-xl text-sm font-medium transition-colors shadow-sm" | |
| style={{ background: '#f43f5e', color: '#fff' }} | |
| onMouseEnter={(e) => (e.currentTarget.style.background = '#e11d48')} | |
| onMouseLeave={(e) => (e.currentTarget.style.background = '#f43f5e')} | |
| > | |
| <Plus className="w-4 h-4" /> | |
| New Session | |
| </button> | |
| </div> | |
| {/* Session List */} | |
| <div className="flex-1 overflow-y-auto px-3 pb-3"> | |
| <div className="flex flex-col gap-1"> | |
| {sessions.length === 0 ? ( | |
| <p className="text-center py-8 text-sm" style={{ color: '#94a3b8' }}>No sessions yet</p> | |
| ) : ( | |
| sessions.map((session) => ( | |
| <button | |
| key={session.id} | |
| onClick={() => setActiveSessionId(session.id)} | |
| className="w-full text-left px-3 py-2.5 rounded-lg text-sm transition-colors flex items-center gap-2.5" | |
| style={{ | |
| background: session.id === activeSessionId ? '#f1f5f9' : 'transparent', | |
| color: session.id === activeSessionId ? '#0f172a' : '#475569', | |
| fontWeight: session.id === activeSessionId ? 500 : 400, | |
| }} | |
| > | |
| <MessageSquare className="w-4 h-4 flex-shrink-0" /> | |
| <span className="truncate">{session.title}</span> | |
| </button> | |
| )) | |
| )} | |
| </div> | |
| </div> | |
| {/* Sidebar Footer Links */} | |
| <div className="p-3 flex-shrink-0" style={{ borderTop: '1px solid #f1f5f9' }}> | |
| <div className="flex flex-col gap-1"> | |
| <Link | |
| href="https://lamatic.ai/docs" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| className="flex items-center gap-2 px-3 py-2 rounded-lg text-sm transition-colors" | |
| style={{ color: '#475569' }} | |
| > | |
| <FileText className="w-4 h-4" style={{ color: '#94a3b8' }} /> | |
| Documentation | |
| </Link> | |
| <Link | |
| href="https://github.com/Lamatic/AgentKit" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| className="flex items-center gap-2 px-3 py-2 rounded-lg text-sm transition-colors" | |
| style={{ color: '#475569' }} | |
| > | |
| <Github className="w-4 h-4" style={{ color: '#94a3b8' }} /> | |
| GitHub | |
| </Link> | |
| </div> | |
| </div> | |
| </aside> | |
| {sidebarOpen && ( | |
| <aside | |
| className="w-72 transition-all duration-300 flex flex-col overflow-hidden flex-shrink-0" | |
| style={{ background: '#fff', borderRight: '1px solid `#e2e8f0`' }} | |
| > | |
| {/* Brand */} | |
| <div className="h-14 flex items-center gap-2 px-5 flex-shrink-0" style={{ borderBottom: '1px solid `#f1f5f9`' }}> | |
| <Stethoscope className="w-5 h-5" style={{ color: '#f43f5e' }} /> | |
| <span className="text-lg font-bold tracking-tight whitespace-nowrap"> | |
| <span style={{ color: '#0f172a' }}>Medical</span>{" "} | |
| <span style={{ color: '#f43f5e' }}>Assistant</span> | |
| </span> | |
| </div> | |
| {/* New Session */} | |
| <div className="p-3 flex-shrink-0"> | |
| <button | |
| onClick={createNewSession} | |
| className="w-full flex items-center justify-center gap-2 px-4 py-2.5 rounded-xl text-sm font-medium transition-colors shadow-sm" | |
| style={{ background: '#f43f5e', color: '#fff' }} | |
| onMouseEnter={(e) => (e.currentTarget.style.background = '#e11d48')} | |
| onMouseLeave={(e) => (e.currentTarget.style.background = '#f43f5e')} | |
| > | |
| <Plus className="w-4 h-4" /> | |
| New Session | |
| </button> | |
| </div> | |
| {/* Session List */} | |
| <div className="flex-1 overflow-y-auto px-3 pb-3"> | |
| <div className="flex flex-col gap-1"> | |
| {sessions.length === 0 ? ( | |
| <p className="text-center py-8 text-sm" style={{ color: '#94a3b8' }}>No sessions yet</p> | |
| ) : ( | |
| sessions.map((session) => ( | |
| <button | |
| key={session.id} | |
| onClick={() => setActiveSessionId(session.id)} | |
| className="w-full text-left px-3 py-2.5 rounded-lg text-sm transition-colors flex items-center gap-2.5" | |
| style={{ | |
| background: session.id === activeSessionId ? '#f1f5f9' : 'transparent', | |
| color: session.id === activeSessionId ? '#0f172a' : '#475569', | |
| fontWeight: session.id === activeSessionId ? 500 : 400, | |
| }} | |
| > | |
| <MessageSquare className="w-4 h-4 flex-shrink-0" /> | |
| <span className="truncate">{session.title}</span> | |
| </button> | |
| )) | |
| )} | |
| </div> | |
| </div> | |
| {/* Sidebar Footer Links */} | |
| <div className="p-3 flex-shrink-0" style={{ borderTop: '1px solid `#f1f5f9`' }}> | |
| <div className="flex flex-col gap-1"> | |
| <Link | |
| href="https://lamatic.ai/docs" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| className="flex items-center gap-2 px-3 py-2 rounded-lg text-sm transition-colors" | |
| style={{ color: '#475569' }} | |
| > | |
| <FileText className="w-4 h-4" style={{ color: '#94a3b8' }} /> | |
| Documentation | |
| </Link> | |
| <Link | |
| href="https://github.com/Lamatic/AgentKit" | |
| target="_blank" | |
| rel="noopener noreferrer" | |
| className="flex items-center gap-2 px-3 py-2 rounded-lg text-sm transition-colors" | |
| style={{ color: '#475569' }} | |
| > | |
| <Github className="w-4 h-4" style={{ color: '#94a3b8' }} /> | |
| GitHub | |
| </Link> | |
| </div> | |
| </div> | |
| </aside> | |
| )} |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/app/page.tsx` around lines 169 - 247, The
sidebar remains mounted and keyboard-focusable when collapsed; change the
rendering so the <aside> is only mounted when sidebarOpen is true (e.g., wrap
the aside JSX with a conditional check on the sidebarOpen state) to remove
hidden focus targets, and ensure any handlers that reference sessions,
createNewSession, setActiveSessionId, or activeSessionId still work when the
sidebar mounts/unmounts.
Comment on lines
+23
to
+28
| ## Output Schema | ||
|
|
||
| | Field | Type | Description | | ||
| | -------- | -------- | ----------------------------------------------------- | | ||
| | `query` | `string` | Max 1000 chars, sanitized for safety | The user's medical question or symptom description | | ||
|
|
Contributor
There was a problem hiding this comment.
Fix malformed table in Output Schema section.
Line 27 has 4 cells but the table header defines only 3 columns, causing rendering issues. Additionally, the output schema appears to duplicate the input field (query) rather than documenting the actual LLM response output.
📝 Proposed fix
## Output Schema
| Field | Type | Description |
| -------- | -------- | ----------------------------------------------------- |
-| `query` | `string` | Max 1000 chars, sanitized for safety | The user's medical question or symptom description |
+| `response` | `string` | The LLM-generated medical information response |Please verify the actual output field name from your Lamatic flow configuration.
📝 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
| ## Output Schema | |
| | Field | Type | Description | | |
| | -------- | -------- | ----------------------------------------------------- | | |
| | `query` | `string` | Max 1000 chars, sanitized for safety | The user's medical question or symptom description | | |
| ## Output Schema | |
| | Field | Type | Description | | |
| | -------- | -------- | ----------------------------------------------------- | | |
| | `response` | `string` | The LLM-generated medical information response | |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/flows/medical-assistant-chat/README.md`
around lines 23 - 28, The Output Schema table is malformed: the row with `query`
has four cells while the header defines three and it incorrectly documents the
input instead of the LLM response; update the table so header and all rows have
the same three columns (Field, Type, Description) and replace the `query` row
with the actual output field name from the Lamatic flow (e.g., `response` or
whatever the flow uses), its type (e.g., `string`), and a concise description of
the model's reply; verify the exact output field name in the
medical-assistant-chat flow configuration and use that identifier in the `Field`
column.
16 tasks
|
Hi @SandipM03! 👋 CodeRabbit has posted actionable review comments on this PR. Please review and address them before requesting a maintainer review. Once you've addressed the CodeRabbit feedback, please push your changes and we'll take another look. Thank you! 🙏 |
d-pamneja
reviewed
Mar 30, 2026
Contributor
There was a problem hiding this comment.
Could you add a live demo link to this file? would allow us to view the functionality better, and allow users to see the kit before forking it. otherwise, LGTM. Thanks!
Contributor
There was a problem hiding this comment.
Also, if you could add the entry in the README.md of the main readme as well?
Author
There was a problem hiding this comment.
Hi, I’ve added the live demo link to the main README as well. Please let me know if anything else is needed.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (3)
kits/assistant/medical-assistant/README.md (1)
4-6:⚠️ Potential issue | 🟡 MinorMission note: the Live Demo badge still dead-ends.
href="#"leaves users with a dead preview entry point. Replace it with the real demo URL or remove the badge until one exists.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/README.md` around lines 4 - 6, The Live Demo badge anchor uses href="#" which creates a dead link; update the anchor in README.md by replacing href="#" with the actual demo URL (the working public demo endpoint) or remove the entire <a> anchor element (or the badge image) until a demo exists, ensuring the badge no longer dead-ends and the alt/title reflect the correct destination.kits/assistant/medical-assistant/.stylelintrc.json (1)
2-17:⚠️ Potential issue | 🟠 MajorMission-critical: CI is still tripping over
@plugin.Static analysis still reports
@pluginas an unknown at-rule inkits/assistant/medical-assistant/app/globals.cssLine 3, so this override is not reaching the rule Stylelint is actually enforcing. Please verify whether the active config comes from a root file or fromscss/at-rule-no-unknown, and mirror the Tailwind ignore list there.#!/bin/bash set -euo pipefail echo "Stylelint configs discovered in the repo:" fd -HI '(^|/)(\.stylelintrc(\..+)?|stylelint\.config\.(js|cjs|mjs|json|yaml|yml))$' . echo echo "Rules that can still reject Tailwind v4 at-rules:" rg -n --hidden --glob '!**/node_modules/**' '(scss/at-rule-no-unknown|at-rule-no-unknown|ignoreAtRules)' . echo echo "Medical assistant local override:" cat kits/assistant/medical-assistant/.stylelintrc.jsonExpected result: the active rule set for this path should ignore
plugin,custom-variant,theme,layer,apply,import, andtailwind.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/.stylelintrc.json` around lines 2 - 17, The CI is still flagging `@plugin` because the active Stylelint rule is coming from the scss plugin or a root config that doesn't include Tailwind at-rules; update the active rule (either the "scss/at-rule-no-unknown" entry or the root "at-rule-no-unknown" in the active config) to include ignoreAtRules with ["apply","custom-variant","import","layer","plugin","tailwind","theme"], or make the medical-assistant .stylelintrc.json extend/override the same rule so the ignore list is mirrored; specifically target the rule name "scss/at-rule-no-unknown" (and/or "at-rule-no-unknown") in your configs and ensure the ignoreAtRules list contains the eight Tailwind entries so `@plugin` is no longer treated as unknown.kits/assistant/medical-assistant/actions/orchestrate.ts (1)
21-24:⚠️ Potential issue | 🟠 MajorMission-critical: close the
anyescape hatch at the server boundary.
data?: anyplus the object branch at Lines 99-100 can still return non-string payloads. The UI consumes this as chat text, so the server action should normalize tostringbefore it crosses the boundary.🎯 One safe way to normalize the payload
): Promise<{ success: boolean - data?: any + data?: string error?: string }> { + const ensureString = (value: unknown): string => { + if (value == null) return "" + return typeof value === "string" ? value : JSON.stringify(value) + } @@ - if (typeof rawAnswer === "object" && rawAnswer !== null) { - answer = rawAnswer.generatedResponse || rawAnswer.text || rawAnswer.content || JSON.stringify(rawAnswer) + if (typeof rawAnswer === "object" && rawAnswer !== null) { + const candidate = + (rawAnswer as any).generatedResponse ?? + (rawAnswer as any).text ?? + (rawAnswer as any).content ?? + rawAnswer + answer = ensureString(candidate) } else if (typeof rawAnswer === "string" && rawAnswer.length > 0) { answer = rawAnswer }Also applies to: 97-103
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/actions/orchestrate.ts` around lines 21 - 24, The server return type currently exposes data?: any; change the Promise generic to use data?: string and ensure every place that sets the data field (notably the object branch around the current lines ~97-103 in orchestrate.ts) normalizes the payload to a string before returning; implement normalization like: if typeof payload === 'string' return it as-is, otherwise return JSON.stringify(payload) (handle null/undefined explicitly as 'null' or empty string per app convention) so the UI always receives a string.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@kits/assistant/medical-assistant/app/page.tsx`:
- Around line 303-317: The textarea composer lacks an accessible name and the
icon-only send button and sticky composer are unlabeled for screen readers; add
an id to the textarea (used by inputRef/handleKeyDown) and connect the visible
label via htmlFor or change the label to a <label> that wraps the textarea so it
is programmatically bound, add an aria-label or aria-labelledby to the sticky
composer container, and give the icon-only send button a clear accessible name
(aria-label or include visually-hidden text) so screen-reader users can identify
and operate the main composer and send action.
In `@kits/assistant/medical-assistant/lib/lamatic-client.ts`:
- Around line 4-8: Remove the MEDICAL_ASSISTANT_CHAT presence check from
lib/lamatic-client.ts so the SDK client initialization is only scoped to SDK
credentials (LAMATIC_API_URL, LAMATIC_PROJECT_ID, LAMATIC_API_KEY); ensure the
module only constructs/exports the Lamatic client (e.g., exported lamaticClient
or createLamaticClient) and does not throw for flow selection, and instead move
or add the MEDICAL_ASSISTANT_CHAT validation into the orchestrator action
(actions/orchestrate.ts) where flows are invoked.
In `@kits/assistant/medical-assistant/README.md`:
- Around line 77-96: Update the unlabeled fenced block that shows the repo tree
in the README.md to use a text language label (i.e., change the opening
backticks to ```text) so markdownlint no longer flags it; locate the repo tree
fenced block (the block starting with "/actions" and listing /app, /components,
/lib, /flows) and add the text label to the fence.
---
Duplicate comments:
In `@kits/assistant/medical-assistant/.stylelintrc.json`:
- Around line 2-17: The CI is still flagging `@plugin` because the active
Stylelint rule is coming from the scss plugin or a root config that doesn't
include Tailwind at-rules; update the active rule (either the
"scss/at-rule-no-unknown" entry or the root "at-rule-no-unknown" in the active
config) to include ignoreAtRules with
["apply","custom-variant","import","layer","plugin","tailwind","theme"], or make
the medical-assistant .stylelintrc.json extend/override the same rule so the
ignore list is mirrored; specifically target the rule name
"scss/at-rule-no-unknown" (and/or "at-rule-no-unknown") in your configs and
ensure the ignoreAtRules list contains the eight Tailwind entries so `@plugin` is
no longer treated as unknown.
In `@kits/assistant/medical-assistant/actions/orchestrate.ts`:
- Around line 21-24: The server return type currently exposes data?: any; change
the Promise generic to use data?: string and ensure every place that sets the
data field (notably the object branch around the current lines ~97-103 in
orchestrate.ts) normalizes the payload to a string before returning; implement
normalization like: if typeof payload === 'string' return it as-is, otherwise
return JSON.stringify(payload) (handle null/undefined explicitly as 'null' or
empty string per app convention) so the UI always receives a string.
In `@kits/assistant/medical-assistant/README.md`:
- Around line 4-6: The Live Demo badge anchor uses href="#" which creates a dead
link; update the anchor in README.md by replacing href="#" with the actual demo
URL (the working public demo endpoint) or remove the entire <a> anchor element
(or the badge image) until a demo exists, ensuring the badge no longer dead-ends
and the alt/title reflect the correct destination.
🪄 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: 9236b580-cb70-45f5-bd2a-3ffacc4b8d5a
📒 Files selected for processing (8)
kits/assistant/medical-assistant/.stylelintrc.jsonkits/assistant/medical-assistant/README.mdkits/assistant/medical-assistant/actions/orchestrate.tskits/assistant/medical-assistant/app/globals.csskits/assistant/medical-assistant/app/page.tsxkits/assistant/medical-assistant/biome.jsonkits/assistant/medical-assistant/flows/medical-assistant-chat/README.mdkits/assistant/medical-assistant/lib/lamatic-client.ts
Comment on lines
+303
to
+317
| <label className="flex items-center gap-2 text-[13px] font-semibold mb-2.5" style={{ color: '#334155' }}> | ||
| <Stethoscope className="w-4 h-4" style={{ color: '#f43f5e' }} /> | ||
| Medical Query or Symptom | ||
| </label> | ||
| <textarea | ||
| ref={inputRef} | ||
| placeholder="e.g. What are the common symptoms of the flu?" | ||
| value={input} | ||
| onChange={(e) => setInput(e.target.value)} | ||
| onKeyDown={handleKeyDown} | ||
| disabled={isLoading} | ||
| rows={3} | ||
| className="w-full resize-none rounded-xl px-4 py-3 text-sm focus:outline-none transition-colors" | ||
| style={{ border: '2px solid #e2e8f0', color: '#1e293b', background: '#fff' }} | ||
| /> |
Contributor
There was a problem hiding this comment.
Mission-critical: the main composer is missing accessible names.
The welcome label is not bound to its <textarea>, the sticky composer has no programmatic label, and the icon-only send button has no accessible name. That blocks the primary chat flow for screen-reader users.
🛰️ Minimal fix
-<label className="flex items-center gap-2 text-[13px] font-semibold mb-2.5" style={{ color: '#334155' }}>
+<label
+ htmlFor="medical-query"
+ className="flex items-center gap-2 text-[13px] font-semibold mb-2.5"
+ style={{ color: '#334155' }}
+>
@@
<textarea
+ id="medical-query"
ref={inputRef}
@@
<textarea
+ aria-label="Describe your symptoms or ask a medical question"
ref={inputRef}
@@
<button
+ aria-label={isLoading ? "Sending medical query" : "Send medical query"}
onClick={handleSend}Also applies to: 478-505
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/app/page.tsx` around lines 303 - 317, The
textarea composer lacks an accessible name and the icon-only send button and
sticky composer are unlabeled for screen readers; add an id to the textarea
(used by inputRef/handleKeyDown) and connect the visible label via htmlFor or
change the label to a <label> that wraps the textarea so it is programmatically
bound, add an aria-label or aria-labelledby to the sticky composer container,
and give the icon-only send button a clear accessible name (aria-label or
include visually-hidden text) so screen-reader users can identify and operate
the main composer and send action.
Comment on lines
+4
to
+8
| if (!process.env.MEDICAL_ASSISTANT_CHAT) { | ||
| throw new Error( | ||
| "MEDICAL_ASSISTANT_CHAT environment variable is not set. Please add it to your .env.local file." | ||
| ); | ||
| } |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Keep the SDK client scoped to SDK credentials.
MEDICAL_ASSISTANT_CHAT is a flow selection concern, not client initialization. Failing on it here couples every lamaticClient import to one specific workflow instead of leaving flow-env validation in actions/orchestrate.ts.
As per coding guidelines, "Use the lib/lamatic-client.ts pattern to initialize the Lamatic SDK with LAMATIC_API_URL, LAMATIC_PROJECT_ID, and LAMATIC_API_KEY" and "Kit server action files (e.g., actions/orchestrate.ts) must call Lamatic flows via the SDK and read flow IDs from environment variables".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/lib/lamatic-client.ts` around lines 4 - 8,
Remove the MEDICAL_ASSISTANT_CHAT presence check from lib/lamatic-client.ts so
the SDK client initialization is only scoped to SDK credentials
(LAMATIC_API_URL, LAMATIC_PROJECT_ID, LAMATIC_API_KEY); ensure the module only
constructs/exports the Lamatic client (e.g., exported lamaticClient or
createLamaticClient) and does not throw for flow selection, and instead move or
add the MEDICAL_ASSISTANT_CHAT validation into the orchestrator action
(actions/orchestrate.ts) where flows are invoked.
Comment on lines
+77
to
+96
| ``` | ||
| /actions | ||
| └── orchestrate.ts # Lamatic workflow orchestration for medical queries | ||
| /app | ||
| ├── globals.css # Teal-themed design system | ||
| ├── layout.tsx # Root layout with SEO metadata | ||
| └── page.tsx # Chat-style medical assistant UI | ||
| /components | ||
| ├── header.tsx # Header with medical branding | ||
| └── disclaimer.tsx # Medical disclaimer components | ||
| /lib | ||
| ├── lamatic-client.ts # Lamatic SDK client | ||
| └── utils.ts # Tailwind class merge utility | ||
| /flows | ||
| └── medical-assistant-chat/ | ||
| ├── config.json # Flow configuration | ||
| ├── inputs.json # Input schema | ||
| ├── meta.json # Flow metadata | ||
| └── README.md # Flow documentation | ||
| ``` |
Contributor
There was a problem hiding this comment.
Mark the repo tree fence as text.
Line 77 starts an unlabeled fenced block, which is already flagged by markdownlint. text is enough here.
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 77-77: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@kits/assistant/medical-assistant/README.md` around lines 77 - 96, Update the
unlabeled fenced block that shows the repo tree in the README.md to use a text
language label (i.e., change the opening backticks to ```text) so markdownlint
no longer flags it; locate the repo tree fenced block (the block starting with
"/actions" and listing /app, /components, /lib, /flows) and add the text label
to the fence.
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (1)
kits/assistant/medical-assistant/README.md (1)
77-96:⚠️ Potential issue | 🟡 MinorMission update: label the repo-structure code fence to clear markdownlint.
Line 77 uses an unlabeled fenced block; change it to ```text to resolve MD040.
🎯 Proposed patch
-``` +```text /actions └── orchestrate.ts # Lamatic workflow orchestration for medical queries /app ... -``` +```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/assistant/medical-assistant/README.md` around lines 77 - 96, The markdown README.md has an unlabeled fenced code block showing the repo tree (around the block starting with "/actions ... /flows"); change the opening fence from ``` to ```text so the block is labeled and satisfies MD040; update the block surrounding the tree in README.md (the repo-structure code fence) to use ```text as the opening fence and keep the closing ``` unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@kits/assistant/medical-assistant/README.md`:
- Around line 77-96: The markdown README.md has an unlabeled fenced code block
showing the repo tree (around the block starting with "/actions ... /flows");
change the opening fence from ``` to ```text so the block is labeled and
satisfies MD040; update the block surrounding the tree in README.md (the
repo-structure code fence) to use ```text as the opening fence and keep the
closing ``` unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro
Run ID: c537fa64-84e8-41df-8b48-743b9b187ad4
📒 Files selected for processing (1)
kits/assistant/medical-assistant/README.md
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
3 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.
What This Kit Does
The Medical Assistant AgentKit is an AI-powered chatbot that provides general medical information, symptom checks, and health guidance through a conversational interface built with Lamatic.ai. It solves the need for accessible, on-demand health information with proper safety guardrails:
Providers & Prerequisites
How to Run Locally
kits/assistant/medical-assistantnpm install.envfile using.env.exampleas a templatenpm run devIssue
Issue: #25
Lamatic Flow
Flow configurations and schemas are maintained in the
flows/medical-assistant-chat/directory of the kit.PR Checklist [Kit]
Kit runs locally with
npm run dev.env.examplehas no secrets, only placeholdersREADME.md
documents setup, environment variables, and usageFolder structure:kits/assistant/medical-assistant/config.jsonandorchestrate.jsare present and validAll flows exported in
flows/folderDemo
Screen.Recording.2026-03-01.165915.mp4
Privacy & Data Handling
Summary
New Features
Configuration
Chores
.gitignoreand build tooling configs includedFlow high-level behavior