chore: setup Kimchi autonomous infrastructure and community templates - #61
Conversation
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
|
Warning Review limit reached
Next review available in: 23 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. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (43)
✨ 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 |
Replace generic PR template with a KeePassBrowserBridge-specific checklist covering Vitest, Playwright, ESLint, .NET plugin builds, Chrome MV3 / Firefox / KeePass impact, security, compatibility, i18n, docs, and CHANGELOG updates. Co-Authored-By: Kimchi <noreply@kimchi.dev>
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
Co-Authored-By: Kimchi <noreply@kimchi.dev>
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
- Remove generated metadata from tracking (.agents, .claude, .codex) - Fix invalid pinned actions/stale SHA to v9.1.0 - Disable autonomous handle-secrets in AUTONOMY.md - Complete major change criteria in AGENTS.md section 20 Co-Authored-By: Kimchi <noreply@kimchi.dev>
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
- Update .github/labeler.yml to actions/labeler v5 syntax - Fix shell quoting for repo_name in four Kimchi workflows - Set AUTONOMY.md owner to hieuck and disable deploy commands - Redirect review output to .kimchi/logs/ in receiving-code-review skill Co-Authored-By: Kimchi <noreply@kimchi.dev>
|
ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR. |
Description
Set up Kimchi autonomous agent infrastructure and complete missing community standards.
Changes
.claude/skills/.claude/ecc-tools.json,.codex/,.agents/, etc.)Motivation
The repository is opted into full continuous operation via
.kimchi/AUTONOMY.md. These files provide the instructions, skills, and automation triggers required for autonomous cycles.Testing
npm test: 1024 passednpm run lint: 0 errors, 0 warnings