chore: remove the Greptile review configuration

[elkaix]

Related Issue

No issue — housekeeping. The problem is described below.

Problem

Greptile's trial credits are exhausted. Both of its "reviews" on #82 are the same notice:

elkaix has reached the 50-credit limit for trial accounts.

Its check still reports success, so a PR looks reviewed by two bots when only CodeRabbit read it. A review bot that passes without reviewing is worse than no bot, because the green check is misleading.

What changed

Removes .greptile/ (config.json, files.json, rules.md). CodeRabbit is unaffected and remains the review bot.

The GitHub App installation is separate from this configuration and is removed through the organization's settings — deleting these files alone does not uninstall it.

Verification

Configuration-only change: no source, tests, or build inputs are touched. git show --stat is three deletions under .greptile/.

Checklist

• I have read the CONTRIBUTING document.
• I have explained the problem above.
• I have added tests that prove my feature works. — not applicable; removes bot configuration only.
• Ran gen-changesets skill, or this PR needs no changeset. — no changeset: nothing published changes.
• Ran gen-docs skill, or this PR needs no doc update.

[greptile-apps]

elkaix has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 11 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 1e0d88e7-da73-4a4c-b71f-4bb5e54dbb8b

📥 Commits

Reviewing files that changed from the base of the PR and between 1cd8682 and 31009aa.

📒 Files selected for processing (3)

• .greptile/config.json
• .greptile/files.json
• .greptile/rules.md

---

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

[pkg-pr-new]

pnpm dlx https://pkg.pr.new/@pymodel/pythinker-code@31009aa

npx https://pkg.pr.new/@pymodel/pythinker-code@31009aa

commit: 31009aa