feat(ci-cd): Add greptile code review configurations

[orama254]

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• All new and existing tests passed.
• This PR does not contain plagiarized content.
• The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
reactdevske-website-vuvs	Ready	Preview	Mar 13, 2026 3:01pm

[greptile-apps]

Greptile Summary

This PR introduces Greptile AI code-review configuration by adding three files under .greptile/: a config.json with branch inclusion, status-check, and strictness settings, plus empty files.json and rules.md placeholders.

Key observations:

• Branch policy violation: This PR targets prod directly instead of routing through develop first. The project's CONTRIBUTING.md, the existing branch-check.yml workflow, the custom review rule auto-9d9c6a6b, and notably the very config.json introduced by this PR all require changes to prod to go through develop first. The branch-check.yml CI check will block this merge as the source branch is not develop.
• Empty rules.md: The .greptile/rules.md file is completely empty. This file is the intended home for detailed, natural-language review rules. Populating it with the project's TypeScript strict-typing requirements, D.R.Y/K.I.S.S principles, and contribution workflow rules would make the Greptile review meaningfully more effective.
• Empty files.json: Similarly empty — no file-specific overrides are defined.
• Missing EOF newline in config.json.

Confidence Score: 1/5

• This PR should not be merged into prod — it must be re-targeted to develop first per project policy.
• The PR directly violates the established branch workflow: CONTRIBUTING.md, the branch-check.yml CI gate, and the custom rule auto-9d9c6a6b all require that changes reach prod only via develop. The existing CI workflow will fail this PR. The configuration files themselves are otherwise low-risk, but the merge target is wrong and cannot be bypassed.
• .greptile/rules.md and .greptile/files.json are empty and should be populated before the configuration is considered complete.

Important Files Changed

Filename	Overview
.greptile/config.json	Adds Greptile configuration with branch inclusion, status checks, and a "prod must go through develop" rule; missing trailing newline at EOF.
.greptile/files.json	Empty placeholder file; no file-specific Greptile overrides are defined, which may be intentional but provides no value as-is.
.greptile/rules.md	Empty rules file; intended to hold project-specific review rules in natural language but currently contains nothing.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Developer opens PR] --> B{Base branch?}
    B -- "develop" --> C[branch-check.yml ✅ PASSES]
    B -- "prod" --> D{Source branch = develop?}
    D -- "Yes" --> E[branch-check.yml ✅ PASSES]
    D -- "No (e.g. feature branch)" --> F[branch-check.yml ❌ FAILS]
    F --> G[Merge blocked]
    C --> H[Greptile review triggered]
    E --> H
    H --> I{config.json rules pass?}
    I -- "Yes" --> J[statusCheck ✅]
    I -- "No" --> K[statusCheck ❌ — blocks merge]
    J --> L[PR approved & merged to develop]
    L --> M[Separate PR: develop → prod]

Loading

Comments Outside Diff (1)

1. .greptile/rules.md, line 1 (link)

   Empty rules file

   rules.md is completely empty. This file is intended to hold detailed Greptile review rules in natural language. Without any content here, Greptile won't have project-specific review guidance to apply beyond what is defined inline in config.json. Consider populating this file with the review rules and coding standards specific to this project (e.g. TypeScript strict typing requirements, D.R.Y/K.I.S.S principles, branch workflow rules, etc.).

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

_{Last reviewed commit: 8e186a2}

[greptile-apps]

Missing newline at end of file

config.json is missing a trailing newline character. Most editors and linters expect files to end with a newline, and the git diff explicitly flags this (\ No newline at end of file).

Suggested change

	}
	}

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}