feat(pr-review): Add missing documentation and changeset checks

[claude]

Summary

This PR improves the automated PR review system based on patterns identified from human reviewer feedback in PR #1699.

Changes

1. Documentation Check (HIGH priority - CRITICAL severity)

File: .claude/agents/pr-review-docs.md

What it does:

• Automatically checks if PR modifies user-facing code without documentation updates
• Triggers on specific file patterns:
  • New UI components: *.tsx in agents-manage-ui/src/components/
  • New API routes: new files in agents-api/src/domains/*/routes/
  • Schema changes: *-schema.ts or packages/agents-core/src/validation/
  • New package exports: package.json exports field changes
  • New SDK patterns: agents-sdk/src/ changes
• Creates CRITICAL finding when documentation is missing

Why this matters:

• AGENTS.md mandates: "ALL new work MUST include... Documentation"
• In PR feat(dashboard): Notify users to enter custom headers if required in chat or if custom headers are invalid #1699, @miles-kt-inkeep had to manually remind: "can you check for docs changes"
• Documentation gaps are commonly forgotten and create support burden

Example finding:

CRITICAL: PR modifies UI components but lacks documentation updates.
Per AGENTS.md: 'ALL new work MUST include... Documentation - Create or update
documentation in /agents-docs/content/docs/'. Users will not know how to use
this new feature/change.

---

2. Changeset Check (HIGH priority - CRITICAL severity)

File: .claude/agents/pr-review-standards.md

What it does:

• Automatically checks if PR modifies published packages without changeset files
• Triggers when PR modifies: agents-core, agents-api, agents-sdk, agents-manage-ui, agents-cli, create-agents, ai-sdk-provider
• Excludes internal-only changes: test files, docs, comment-only changes
• Creates CRITICAL finding when changeset is missing

Why this matters:

• AGENTS.md mandates: "Create a changeset for any user-facing change to a published package"
• In PR feat(dashboard): Notify users to enter custom headers if required in chat or if custom headers are invalid #1699, @dimaMachina had to manually request: "can you write a changeset"
• Missing changesets break semantic versioning workflow and changelog tracking

Example finding:

CRITICAL: PR modifies published packages [agents-core, agents-manage-ui] but
lacks a changeset. Per AGENTS.md: 'Create a changeset for any user-facing
change to a published package.' Version bumps won't be tracked. Package
changes won't appear in changelog.

Fix: Run: pnpm bump <patch|minor|major> --pkg <package-name> "<description>"

---

3. React Compiler Annotation Fix (MEDIUM priority - Bug fix)

File: .claude/agents/pr-review-frontend.md

What it does:

• Recognizes 'use memo' and 'use no memo' as valid React Compiler annotations
• Prevents false positives when these directives are used
• References official React documentation: https://react.dev/learn/react-compiler#annotations

Why this matters:

• In PR feat(dashboard): Notify users to enter custom headers if required in chat or if custom headers are invalid #1699, the bot incorrectly flagged 'use memo' as an invalid directive
• @dimaMachina had to provide a Next.js documentation link to correct the bot
• This created noise and wasted reviewer time

---

Methodology

These improvements were identified through systematic analysis of PR #1699:

1. Compared human reviewer comments vs automated bot comments
2. Identified patterns humans caught that bots missed
3. Applied 4 generalizability criteria (all must pass):
   • ✅ Actionable: Can be turned into a specific check/rule
   • ✅ Frequent: Likely to recur in future PRs
   • ✅ Objectively verifiable: Can be checked programmatically
   • ✅ Not already covered: Not duplicating existing bot checks

Result: 2 HIGH-generalizability patterns + 1 bug fix identified

---

Impact

Before this PR:

• Human reviewers had to manually remind about documentation
• Human reviewers had to manually request changesets
• Bot created false positives for React Compiler annotations

After this PR:

• Bot automatically checks for missing documentation (CRITICAL finding)
• Bot automatically checks for missing changesets (CRITICAL finding)
• Bot correctly recognizes React Compiler annotations (no false positives)

---

Testing Recommendation

To validate these changes work correctly:

1. Create a test PR that modifies agents-manage-ui/src/components/ without docs → should trigger CRITICAL finding
2. Create a test PR that modifies packages/agents-core/ without changeset → should trigger CRITICAL finding
3. Create a test PR with 'use memo' directive → should NOT flag as error

---

Related

• Source PR: feat(dashboard): Notify users to enter custom headers if required in chat or if custom headers are invalid #1699
• Analysis agent: closed-pr-review-auto-improver
• Human reviewers: @miles-kt-inkeep, @dimaMachina, @sarah-inkeep

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agents-api	Ready	Preview, Comment	Feb 6, 2026 7:00am
agents-docs	Ready	Preview, Comment	Feb 6, 2026 7:00am
agents-manage-ui	Ready	Preview, Comment	Feb 6, 2026 7:00am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7d9621e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[nick-inkeep]

Closing - PR body still too verbose (had extra sections). Updated agent with stricter template.