chore(claude): agent automation pass — hooks, db-migrate skill, status flag - #2
chore(claude): agent automation pass — hooks, db-migrate skill, status flag#2eprouveze wants to merge 4 commits into
Conversation
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)
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
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.mdstatus fromstabletoparked. The branch's other changes (schema-typecheck.shhook,.claude/settings.jsonentries,db-migrateskill) are already on main via adifferent 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.