feat: [kit] Add Local Infrastructure Risk Analyzer for municipal project risk assessment#255
feat: [kit] Add Local Infrastructure Risk Analyzer for municipal project risk assessment#255shwetaa188 wants to merge 9 commits into
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughChangesThe Infrastructure Risk Analyzer kit adds Lamatic configuration, model and prompt definitions, a webhook-driven analysis flow, agent governance guidance, and documentation for producing stakeholder risk matrices from infrastructure project and location inputs. Infrastructure Risk Analyzer
Suggested reviewers: 🚥 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 |
|
/label agentkit-challenge |
akshatvirmani
changed the title
:robot_face: AgentKit Structural ValidationNew Contributions Detected
Check Results
🎉 All checks passed! This contribution follows the AgentKit structure. |
|
Failure recorded at 2026-07-20T09:55:25Z UTC. If this PR is not fixed within 4 weeks it will be automatically closed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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/infrastructure-risk-analyzer/README.md`:
- Around line 5-8: Update the README.md for the infrastructure risk analyzer to
include the kit’s mandatory human-readable setup guide, using the repository’s
established setup-guide content or format. Also add the required blank line
after the heading and ensure the file ends with a trailing newline, without
changing the existing workflow description.
🪄 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: 5bd8c501-2e88-48ad-a18e-6b758dbe0ee5
📒 Files selected for processing (5)
kits/infrastructure-risk-analyzer/README.mdkits/infrastructure-risk-analyzer/flows/infra-risk-flow.jsonkits/infrastructure-risk-analyzer/lamatic.config.tskits/infrastructure-risk-analyzer/model-configs/llama-3.3.jsonkits/infrastructure-risk-analyzer/prompts/risk_analysis.prompt
|
Hi @shwetaa188! 👋 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! 🙏 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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/infrastructure-risk-analyzer/agent.md`:
- Around line 3-16: Update the markdown structure in the Overview, Purpose, and
Capabilities sections by adding a blank line immediately after each heading, and
ensure the document ends with exactly one newline.
In `@kits/infrastructure-risk-analyzer/flows/infrastucture-risk-analyzer.ts`:
- Around line 2-6: Complete the executable flow contract represented by the
exported flow object by adding its required inputs, references, nodes, and edges
as a self-contained structure, or relocate this metadata-only descriptor outside
the flows directory so runtime discovery does not load it as a flow.
🪄 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: 6b65e8e6-5d4a-4292-8ad2-9ea8587baa0f
📒 Files selected for processing (4)
kits/infrastructure-risk-analyzer/README.mdkits/infrastructure-risk-analyzer/agent.mdkits/infrastructure-risk-analyzer/constitutions/default.mdkits/infrastructure-risk-analyzer/flows/infrastucture-risk-analyzer.ts
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/infrastructure-risk-analyzer/README.md`:
- Line 15: Update the workflow endpoint testing step in the README to include a
sample request payload containing both required fields, project_description and
location, so users can successfully test the endpoint with sample infrastructure
project text.
🪄 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: bdd3a4af-7893-4c99-afc3-c05b5f6bb647
📒 Files selected for processing (1)
kits/infrastructure-risk-analyzer/README.md
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/infrastructure-risk-analyzer/flows/infrastucture-risk-analyzer.ts`:
- Around line 5-34: Complete the exported infrastructure risk analyzer flow by
adding the required top-level meta, inputs, references, and edges members.
Define inputs for project_description and location, reference the LLM prompt
explicitly through references, and connect the webhook trigger to
web_search_node, then to llm_analysis_node, and finally to the declared output
so the graph is executable.
🪄 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: f44fe053-3962-4de0-b674-e7bc2ae58e14
📒 Files selected for processing (2)
kits/infrastructure-risk-analyzer/agent.mdkits/infrastructure-risk-analyzer/flows/infrastucture-risk-analyzer.ts
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/infrastructure-risk-analyzer/lamatic.config.ts`:
- Around line 11-14: Update the links.github configuration in the links object
to use the full URL
https://github.com/Lamatic/AgentKit/tree/main/kits/infrastructure-risk-analyzer
instead of the relative repository path.
🪄 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: 83c93270-8a06-462e-af3b-036efea346f1
📒 Files selected for processing (1)
kits/infrastructure-risk-analyzer/lamatic.config.ts
Added additional guidelines for tone and content generation.
|
Hi @amanintech @d-pamneja, all CI checks are passing and CodeRabbit has approved the changes. Ready for your final review! |
1 participant
PR Checklist
1. Select Contribution Type
kits/<category>/<kit-name>/)bundles/<bundle-name>/)templates/<template-name>/)2. General Requirements
kebab-caseand matches the flow IDREADME.md(purpose, setup, usage)3. File Structure (Check what applies)
config.jsonpresent with valid metadata (name, description, tags, steps, author, env keys)flows/<flow-name>/(where applicable) include:config.json(Lamatic flow export)inputs.jsonmeta.jsonREADME.md.env.examplewith placeholder values only (kits only)config.jsonnode graphs (changes via Lamatic Studio export)4. Validation
npm install && npm run devworks locally (kits: UI runs; bundles/templates: flows are valid)[kit] Add <name> for <use case>)kits/infrastructure-risk-analyzer/README.mddocumenting the agent, its Input → Analysis → Output workflow, and setup/testing steps (env configuration, local/Lamatic execution, and webhook workflow testing).kits/infrastructure-risk-analyzer/agent.mddescribing the agent’s purpose and capabilities, including producing a Stakeholder Risk Matrix with mitigation strategies.kits/infrastructure-risk-analyzer/constitutions/default.mddefining the assistant’s role, safety/refusal behavior, data-handling expectations, and professional tone.kits/infrastructure-risk-analyzer/prompts/risk_analysis.promptto generate a structured Stakeholder Risk Matrix (Risk Title, Impact Level, Affected Stakeholders, Mitigation Strategy) fromproject_description+location.kits/infrastructure-risk-analyzer/model-configs/llama-3.3.jsonconfiguring Groqllama-3.3-70b-versatile(e.g.,temperature: 0.7,max_tokens: 1024).kits/infrastructure-risk-analyzer/lamatic.config.tswith kit metadata (name/description/version/tags/author) and a single mandatory stepexecuteWorkflow, pluslinks.githubpointing tokits/infrastructure-risk-analyzer(andlinks.deployleft blank).kits/infrastructure-risk-analyzer/flows/infra-risk-flow.jsondefining the flow’s webhook-based execution:project_descriptionandlocationtoolWeb Search (query template uses{location}) →llmRisk Analyzer Core (modelllama-3.3-70b, prompt reference tokits/infrastructure-risk-analyzer/prompts/risk_analysis.prompt)status(string) andresult(object)kits/infrastructure-risk-analyzer/flows/infrastucture-risk-analyzer.tsexporting the TypeScript flow definition with the same webhook schema andtool→llmnode chain and matchingstatus/resultoutput contract (including a prompt reference to the risk analysis prompt).