Fetch open review comments on the current branch's PR (Greptile, human reviewers, etc.) and remediate each one — either by fixing the code, explaining why the comment does not apply, or flagging it for the user. Use when asked to "address PR comments", "fix Greptile findings", or whenever the check-changed-folders…
Run typecheck, tests, and builds for Rudder's core and plugin workspaces on the current branch versus main, verify Claude/Codex provider parity, verify the centralized agent-instruction layout, and verify agent attribution. Use when asked to run "/check", to validate a branch before commit/PR, whenever a user asks to…
Create and validate Rudder's Drizzle-backed local SQLite migrations. Use when changing src/db/schema.ts, generating or reviewing files under drizzle/, adding or altering database tables, columns, constraints, or indexes, writing data backfills, or troubleshooting migration failures in rudder.db.
Apply and verify Rudder's no-greptile pull-request label. Use when creating, updating, or reviewing a PR that the user explicitly wants to exclude from Greptile automated review.
Prepare and validate Rudder plugin version bumps, including synchronized package/plugin manifests and a CodeAlmanac wiki refresh. Use whenever changing the version in package.json, package-lock.json, .codex-plugin/plugin.json, .claude-plugin/plugin.json, or .claude-plugin/marketplace.json; when asked to bump, cut, or…
Instructions for RudderCode/Rudder, a project described as: Make your specs actually comprehensive. Pair your specs with tests to make your coding agent stop improvising bad code.
Use locally captured coding-session intent to resolve a device-local behavioral spec, generate focused tests from that spec, implement the smallest production changes through red-green TDD, and verify coverage with the repository's native tooling. Use when the user asks to run Rudder, create or regenerate tests for…