feat(blog): add How Prisma Builds with Agentic AI post#7684
Open
ArthurGamby wants to merge 3 commits intomainfrom
Open
feat(blog): add How Prisma Builds with Agentic AI post#7684ArthurGamby wants to merge 3 commits intomainfrom
ArthurGamby wants to merge 3 commits intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
WalkthroughAdded a new MDX blog post documenting Prisma’s agentic engineering practices, including spec-first design, adversarial spec reviews, a trust-ladder for delegation, local agent verification loops, and guidance on tests and human review. (48 words) Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx (1)
2-3: Align title and slug phrasing for URL consistencyLine 2 uses “Builds” while Line 3 uses “build”. Consider updating the slug to
how-prisma-builds-with-agentic-aiso permalink grammar matches the published title and avoids awkward URL phrasing.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx` around lines 2 - 3, The title and slug are inconsistent: the frontmatter key "title" is "Agentic Engineering: How Prisma Builds with AI" while the "slug" uses "how-prisma-build-with-agentic-ai"; update the slug value to "how-prisma-builds-with-agentic-ai" so the slug grammar matches the title ("Builds") and the permalink reads naturally, ensuring you modify the "slug" line in the file to the new value.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx`:
- Around line 2-3: The title and slug are inconsistent: the frontmatter key
"title" is "Agentic Engineering: How Prisma Builds with AI" while the "slug"
uses "how-prisma-build-with-agentic-ai"; update the slug value to
"how-prisma-builds-with-agentic-ai" so the slug grammar matches the title
("Builds") and the permalink reads naturally, ensuring you modify the "slug"
line in the file to the new value.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 3fa91cba-1f9d-4c60-81a5-3c4573ea5fe7
⛔ Files ignored due to path filters (4)
apps/blog/public/authors/arthur-gamby.pngis excluded by!**/*.pngapps/blog/public/how-prisma-build-with-agentic-ai/imgs/local-feedback-loop.pngis excluded by!**/*.pngapps/blog/public/how-prisma-build-with-agentic-ai/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/how-prisma-build-with-agentic-ai/imgs/the-trust-ladder.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx
Replace raw markdown blockquotes with the blog's <Quotes> component for consistent styling with speaker name and position attribution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx`:
- Around line 2-3: The slug in the frontmatter uses
"how-prisma-build-with-agentic-ai" which conflicts with the title "Agentic
Engineering: How Prisma Builds with AI"; update the slug to
"how-prisma-builds-with-agentic-ai" and also rename or update any related
asset/path names and internal links referenced elsewhere in this file (the
entries around the other frontmatter/asset lines) so they consistently use
"builds" to match the title and avoid URL/SEO mismatches.
- Line 112: Replace the non-hyphenated compound "error handling strategy" with
the hyphenated compound "error-handling strategy" in the sentence that currently
reads "Agents don't know what they don't know about your system...or the error
handling strategy that accounts for a third-party service's quirky failure
modes." Update that exact phrase to "error-handling strategy" to use the correct
compound modifier.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d18af161-15ee-4c5b-a1c1-c8634372fcac
📒 Files selected for processing (1)
apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx
Comment on lines
+2
to
+3
| title: "Agentic Engineering: How Prisma Builds with AI" | ||
| slug: "how-prisma-build-with-agentic-ai" |
Contributor
There was a problem hiding this comment.
Align slug/path wording with the published title.
Line 3 uses how-prisma-build-with-agentic-ai while the title uses “Builds.” This can create avoidable URL inconsistency across social shares/SEO metadata. Consider standardizing on “builds” (and matching asset path naming if you change the slug).
Also applies to: 9-10
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx` around
lines 2 - 3, The slug in the frontmatter uses "how-prisma-build-with-agentic-ai"
which conflicts with the title "Agentic Engineering: How Prisma Builds with AI";
update the slug to "how-prisma-builds-with-agentic-ai" and also rename or update
any related asset/path names and internal links referenced elsewhere in this
file (the entries around the other frontmatter/asset lines) so they consistently
use "builds" to match the title and avoid URL/SEO mismatches.
|
|
||
| When mechanical coding is automated, engineers don't become less important, they operate at a higher level of abstraction. The work that matters most, system design, observability, error handling, edge cases, is exactly the work that requires deep human understanding of the problem domain. | ||
|
|
||
| Agents don't know what they don't know about your system. They can't anticipate the edge case that surfaces under a specific load pattern, or the error handling strategy that accounts for a third-party service's quirky failure modes. |
Contributor
There was a problem hiding this comment.
Use a hyphenated compound modifier for clarity.
At Line 112, “error handling strategy” reads better as “error-handling strategy” in this usage.
✏️ Suggested wording tweak
-Agents don't know what they don't know about your system. They can't anticipate the edge case that surfaces under a specific load pattern, or the error handling strategy that accounts for a third-party service's quirky failure modes.
+Agents don't know what they don't know about your system. They can't anticipate the edge case that surfaces under a specific load pattern, or the error-handling strategy that accounts for a third-party service's quirky failure modes.🧰 Tools
🪛 LanguageTool
[grammar] ~112-~112: Use a hyphen to join words.
Context: ...er a specific load pattern, or the error handling strategy that accounts for a th...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/blog/content/blog/how-prisma-build-with-agentic-ai/index.mdx` at line
112, Replace the non-hyphenated compound "error handling strategy" with the
hyphenated compound "error-handling strategy" in the sentence that currently
reads "Agents don't know what they don't know about your system...or the error
handling strategy that accounts for a third-party service's quirky failure
modes." Update that exact phrase to "error-handling strategy" to use the correct
compound modifier.
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
1 participant
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.
Summary
Voice audit (
devrel-voice)Passes:
Minor flags (cosmetic, not blocking):
Recommendation: No voice pass needed. The post is already well within Prisma voice guidelines. It leads with usefulness, sounds like a person, is honest about tradeoffs, and has a pulse. Running
devrel-voiceon it would risk over-polishing writing that already works.Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit