Improvement] Fix metadata links, setup docs, and env placeholders#71
Merged
amanintech merged 2 commits intoLamatic:mainfrom Mar 23, 2026
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughBundle and kit metadata URLs and README license paths were corrected; numerous .env.example files were reformatted (removed spaces around Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
kits/sample/content-generation/README.md (1)
12-12:⚠️ Potential issue | 🟠 MajorDeploy button still points at a different kit.
Line 12 still sets
root-directory=kits/agentic/generation, but this README is forkits/sample/content-generation. Users following this page will deploy the wrong subdirectory.Suggested fix
-[](https://vercel.com/new/clone?repository-url=https://github.com/Lamatic/AgentKit&root-directory=kits/agentic/generation&env=AGENTIC_GENERATE_CONTENT,LAMATIC_API_URL,LAMATIC_PROJECT_ID,LAMATIC_API_KEY&envDescription=Your%20Lamatic%20Generation%20keys%20are%20required.&envLink=https://lamatic.ai/templates/agentkits/agentic/agent-kit-generation) +[](https://vercel.com/new/clone?repository-url=https://github.com/Lamatic/AgentKit&root-directory=kits/sample/content-generation&env=AGENTIC_GENERATE_CONTENT,LAMATIC_API_URL,LAMATIC_PROJECT_ID,LAMATIC_API_KEY&envDescription=Your%20Lamatic%20Generation%20keys%20are%20required.&envLink=https://lamatic.ai/templates/agentkits/agentic/agent-kit-generation)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@kits/sample/content-generation/README.md` at line 12, The deploy badge in README.md points to the wrong subdirectory: update the URL query parameter root-directory in the Vercel button link (the string containing root-directory=kits/agentic/generation) to root-directory=kits/sample/content-generation so the badge deploys the correct kit; ensure the rest of the query (repository-url and env/envDescription/envLink) remains unchanged and verify the rendered badge link opens the desired subdirectory.
🧹 Nitpick comments (1)
README.md (1)
131-133: Mention copying from the kit’s.env.examplefirst.Right now this tells users where to enter values, but not how to get the kit-specific variable list. Since the kits already ship
.env.exampletemplates, adding that step would prevent missing or mistyped keys.Suggested wording
- - Enter API keys, endpoints, and credentials in `.env` or `.env.local` (based on the selected kit). Setup details are documented in each kit/template `README.md`. + - Copy the selected kit’s `.env.example` to `.env` or `.env.local`, then fill in the required API keys, endpoints, and credentials. Setup details are documented in each kit/bundle `README.md`.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 131 - 133, Update the "3. **Configure Integrations**" step in README.md to instruct users to first copy the kit's `.env.example` into `.env` or `.env.local` before filling values, e.g. "cp .env.example .env" (or use the equivalent on Windows), and mention that each kit/template ships its own `.env.example` with the full variable list; reference the existing sentence that tells users to enter API keys/endpoints so the new line appears directly before it and prevents missing or mistyped keys.
🤖 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/embed/sheets/.env.example`:
- Around line 1-4: The .env example uses spaces around the equals sign which
breaks canonical dotenv syntax; update the variables EMBEDDED_SHEETS,
LAMATIC_API_URL, LAMATIC_PROJECT_ID, and LAMATIC_API_KEY to standard KEY="value"
format with no spaces around '=' (e.g., EMBEDDED_SHEETS="EMBEDDED_SHEETS Flow
ID") so the file is safe to source and stops dotenv-linter warnings.
In `@README.md`:
- Around line 124-129: Update the README text that directs users to "/templates"
so it matches the repository structure in this PR by replacing references to
"/templates" with "bundles/..." (or reword to "browse bundles for single-flow
exports") where the example and bullet list mention "/templates"; ensure the
example path and explanatory line that currently reads "/templates" now points
to the correct "bundles" location so users are not sent to a non-existent path.
---
Outside diff comments:
In `@kits/sample/content-generation/README.md`:
- Line 12: The deploy badge in README.md points to the wrong subdirectory:
update the URL query parameter root-directory in the Vercel button link (the
string containing root-directory=kits/agentic/generation) to
root-directory=kits/sample/content-generation so the badge deploys the correct
kit; ensure the rest of the query (repository-url and
env/envDescription/envLink) remains unchanged and verify the rendered badge link
opens the desired subdirectory.
---
Nitpick comments:
In `@README.md`:
- Around line 131-133: Update the "3. **Configure Integrations**" step in
README.md to instruct users to first copy the kit's `.env.example` into `.env`
or `.env.local` before filling values, e.g. "cp .env.example .env" (or use the
equivalent on Windows), and mention that each kit/template ships its own
`.env.example` with the full variable list; reference the existing sentence that
tells users to enter API keys/endpoints so the new line appears directly before
it and prevents missing or mistyped keys.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 129058cb-e115-4b03-b209-81322a6b7cf5
📒 Files selected for processing (16)
README.mdbundles/assistants/config.jsonbundles/document-parsing/config.jsonbundles/knowledge-chatbot/config.jsonbundles/sample/chatbot/config.jsonbundles/semantic-search/config.jsonkits/agentic/generation/README.mdkits/assistant/grammar-extension/README.mdkits/assistant/grammar-extension/config.jsonkits/automation/blog-automation/.env.examplekits/automation/hiring/README.mdkits/embed/chat/README.mdkits/embed/search/README.mdkits/embed/sheets/.env.examplekits/embed/sheets/README.mdkits/sample/content-generation/README.md
amanintech
approved these changes
Mar 23, 2026
amanintech
approved these changes
Mar 23, 2026
Member
|
Good contributions and fixes @amanyadav721 . Thanks for your contributions. Please check out https://lamatic.ai/careers |
Contributor
Author
|
Already scheduled a meet on 3 April
…On Mon, 23 Mar 2026 at 21:18, Aman Sharma ***@***.***> wrote:
*amanintech* left a comment (Lamatic/AgentKit#71)
<#71 (comment)>
Good contributions and fixes @amanyadav721
<https://github.com/amanyadav721> . Thanks for your contributions. Please
check out https://lamatic.ai/careers
—
Reply to this email directly, view it on GitHub
<#71?email_source=notifications&email_token=ALQCYUTY23KVYLWWTXAZJL34SFMD5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJRGE3DKMBZGUZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4111650952>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQCYURI2HOYKVZFDKGHDD34SFMD5AVCNFSM6AAAAACWJ3YYG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMJRGY2TAOJVGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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
2 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.
Fix invalid githubUrl values in bundle/kit config.json
Correct root setup instructions in README.md (kits path + run commands)
Fix copied env placeholders in Sheets and Blog Automation examples
Fix broken local README links to LICENSE by pointing to repo root
Minor grammar-extension README link fix (lamatic-config-example.json)
Summary by CodeRabbit
Documentation
Chores