Skip to content

chore(claude): agent automation pass — hooks, db-migrate skill, status flag - #2

Open
eprouveze wants to merge 4 commits into
mainfrom
pr/chore-claude-automation-pass
Open

chore(claude): agent automation pass — hooks, db-migrate skill, status flag#2
eprouveze wants to merge 4 commits into
mainfrom
pr/chore-claude-automation-pass

Conversation

@eprouveze

Copy link
Copy Markdown
Owner

Branch-audit SAFE-MERGE candidate: chore/claude-automation-pass (3 commits, 2026-06-11).

Real net diff vs main is small — flips .claude/project-intel.md status from
stable to parked. The branch's other changes (schema-typecheck.sh hook,
.claude/settings.json entries, db-migrate skill) are already on main via a
different path, so the merge is effectively just the status flag.

Verdict evidence: clean merge, no conflicts. Not health-data-handling code —
agent tooling metadata only, so the HealthPulse health-data caution doesn't apply.

One thing worth a human gut-check before merging: is "status: parked" still
accurate as of today (2026-07-03, over 3 weeks after this branch's last commit)?
This flips a project status flag and that fact itself could be stale.

Not merging this myself — opened for review/merge per the audit's execution model.
Full report: lex/docs/stats/branch-audit-2026-07-03/misc-group.md.

eprouveze and others added 4 commits June 7, 2026 11:54
Deleted 7 placeholder fleet-template agents; added schema.ts PostToolUse tsc hook + db-migrate skill (backup-gated Drizzle migrate). Part of fleet global-vs-local automation pass (lex decision 2026-06-07).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reverts the placeholder-agent deletions: those are fleet-managed common
templates (fleet/common/agents/*.template.md), re-deployed by fleet-sync.
Deleting them per-repo is futile + fights the fleet system. This PR keeps
ONLY the bespoke additions (hooks/skills). Decision: lex 2026-06-07.
…ma-typecheck hook, db-migrate skill, project-intel status)
@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@eprouveze, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 63e08975-b1eb-4323-b255-d885dac1ef79

📥 Commits

Reviewing files that changed from the base of the PR and between 1734cc0 and 8aca271.

📒 Files selected for processing (1)
  • .claude/project-intel.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch pr/chore-claude-automation-pass

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant