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 1 commit into
Conversation
WalkthroughChangesInfrastructure Risk Analyzer
🚥 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
❌ Errors
|
|
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
| ## How it works | ||
| 1. **Input:** Takes a project proposal description or text documentation. | ||
| 2. **Analysis:** Orchestrates workflow nodes to extract risk parameters and cross-reference potential local impacts. | ||
| 3. **Output:** Formats a clean, actionable **Stakeholder Risk Matrix**. No newline at end of file |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Incorporate the mandatory setup guide and resolve formatting anomalies.
Agent, we have a breach in protocol. The dossier (README.md) is missing critical operational parameters—specifically, the mandatory human-readable setup guide required for field deployment. Furthermore, our static analysis intercepts indicate minor formatting anomalies (missing blank line after the heading and missing trailing newline). As per coding guidelines, each kit must contain a README.md file with a human-readable setup guide. Your mission, should you choose to accept it, is to integrate the setup guide and resolve the spacing issues to ensure the package meets agency standards.
🕵️♂️ Proposed mission parameters (fix)
-## How it works
-1. **Input:** Takes a project proposal description or text documentation.
-2. **Analysis:** Orchestrates workflow nodes to extract risk parameters and cross-reference potential local impacts.
-3. **Output:** Formats a clean, actionable **Stakeholder Risk Matrix**.
+## How it works
+
+1. **Input:** Takes a project proposal description or text documentation.
+2. **Analysis:** Orchestrates workflow nodes to extract risk parameters and cross-reference potential local impacts.
+3. **Output:** Formats a clean, actionable **Stakeholder Risk Matrix**.
+
+## Setup Guide
+
+1. Clone the repository and navigate to the `kits/infrastructure-risk-analyzer` directory.
+2. Deploy the kit using the Lamatic platform.
+3. Configure any required webhook endpoints or API keys.📝 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.
| ## How it works | |
| 1. **Input:** Takes a project proposal description or text documentation. | |
| 2. **Analysis:** Orchestrates workflow nodes to extract risk parameters and cross-reference potential local impacts. | |
| 3. **Output:** Formats a clean, actionable **Stakeholder Risk Matrix**. | |
| ## How it works | |
| 1. **Input:** Takes a project proposal description or text documentation. | |
| 2. **Analysis:** Orchestrates workflow nodes to extract risk parameters and cross-reference potential local impacts. | |
| 3. **Output:** Formats a clean, actionable **Stakeholder Risk Matrix**. | |
| ## Setup Guide | |
| 1. Clone the repository and navigate to the `kits/infrastructure-risk-analyzer` directory. | |
| 2. Deploy the kit using the Lamatic platform. | |
| 3. Configure any required webhook endpoints or API keys. |
🧰 Tools
🪛 markdownlint-cli2 (0.23.0)
[warning] 5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 8-8: Files should end with a single newline character
(MD047, single-trailing-newline)
🤖 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/infrastructure-risk-analyzer/README.md` around lines 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.
Sources: Coding guidelines, Linters/SAST tools
|
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! 🙏 |
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>)README.mddocumenting the agent’s purpose, workflow, inputs, and Stakeholder Risk Matrix output.infra-risk-flow.jsonflow:project_descriptionandlocation.risk_analysis.prompt, which directs the model to identify environmental, community, and structural risks and provide impact levels, affected stakeholders, and mitigation strategies.lamatic.config.tswith kit metadata, author information, tags, version, and workflow execution setup.