Assess feature requests and proposals against a project's written direction and maintainer comments. Produce a verdict with supporting evidence, draft replies, and document new decisions against features while leaving final decisions to maintainers.
Assess pull requests from external contributors for safety, scope, bug evidence, and outstanding requirements. Produce a verdict table with supporting evidence and draft replies to help maintainers decide what should happen next.
Review TypeScript type assertions, which tell the compiler to treat a value as a chosen type. Replace bare casts with better types or runtime checks, and use explicit helpers with specific reasons when an escape hatch remains necessary.
Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.
Refactor TypeScript code that handles several variants in multiple places using frozen classes and a Visitor interface, which defines a handler for each variant. This helps type checking expose missing handlers when new variants are added.
Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.
Capture unexpected behavior and workarounds encountered while using Prisma 8, Prisma Compute, or Prisma Postgres. Record symptoms, causes, versions, and reproduction steps in a local log linked to a Linear ticket, checking for duplicates first.
Coordinate GitHub pull request reviews by assigning comment triage and code changes to dedicated sub-agents. Repeat the process, track decisions and progress, and reply to and resolve threads as fixes are completed.
Write Git commit messages with a summary and body through the Shell tool using single-quoted text with actual newlines. This avoids quoting failures that can put command syntax into the saved commit message.
Collect and validate the review state of a GitHub pull request, then generate a readable Markdown report, a text summary, and a list of items to address before review triage begins.
Prepare the next Prisma 8 release by updating workspace versions, assembling upgrade guides, and drafting release notes. Open release and documentation pull requests for maintainer review; merging the release request triggers automated publication.
Create or edit Markdown with each prose paragraph on one source line, letting the viewer wrap the text automatically. Preserve meaningful line breaks in lists, code, and poetry while reducing unnecessary changes in file comparisons.
Create GitHub pull requests for Prisma 8 with Linear ticket IDs in their titles. Turn branch changes into a clear description covering concrete examples, design decisions, behavior changes, and testing evidence for reviewers.
Implement PR review actions already selected for fixes, run relevant checks, and create focused commits. Post progress and completion replies, resolve applicable threads, and update the action records and their Markdown summary.
Prepare and open a pull request for an external contribution to prisma/orm. Check contribution rules, change scope, tests, and contributor signoffs, then draft the title and explanation for approval before submitting from a fork.
Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.
Guide code that consumes PSL parser output by choosing the right syntax tree layer. Use typed AST classes for structure and navigation helpers for positions, while avoiding text parsing shortcuts and direct access to internal storage.
Guide Prisma 8 development by selecting task-specific references for data definitions, queries, migrations that change database structure, runtime setup, debugging, and upgrades. Check package versions and generated contract files before proceeding with implementation.
Record migration instructions for Prisma 8 breaking changes alongside the pull request. Prepare separate guidance for application users and extension authors, with optional code transformation scripts and checks that reproduce the required changes.
Write or revise system architecture documents, design decision records, and engineering references. Use concrete examples and clear explanations of design choices to make documents useful both to newcomers and to developers needing precise details.
Turn previously fetched pull request reviews into an ordered action plan. Separate distinct findings, track deferred work in Linear, validate that every triage decision is complete, and produce JSON and Markdown files for the implementation phase.
Helps build and maintain shadcn/ui projects by finding, adding, styling, debugging, and composing components. It uses project configuration and component documentation to guide implementation across registries, presets, and supported project setups.
Use when the operator wants a page that answers one specific developer question, such as a comparison ("Prisma vs X", "X vs Y"), an alternatives page ("X alternatives"), a roundup ("best X for Y"), a use-case guide ("Postgres for X", "where to host X"), or a troubleshooting fix; when they give a question from the content tracker or its tracker reference; or when they want to publish such a page so readers, search engines and agents can find it.
The English summary is being prepared. Showing the original description.
Use when adding a new docs section or product area, editing llms.ts / the llms.txt or llms/[...slug] / llms-full.txt routes / get-llm-text / skill.md / .well-known endpoints, or working on the "agent score", "llms.txt", or anything "agent-ready" in the docs and site apps. Explains the invariants the Mintlify agent-readiness audit measures and how to hold them.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)