PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Evaluate verified findings from merge-ready, Greptile, pull-request, CI, security, billing, and other code reviews, then promote durable review gaps into the version-controlled .greptile…
Install Maintain Greptile Rules
$ npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jwuthri/Tracely-ai maintain-greptile-rules --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jwuthri/Tracely-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/maintain-greptile-rules .claude/skills/maintain-greptile-rules && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "maintain-greptile-rules" agent skill from https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rules into .claude/skills/maintain-greptile-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-greptile-rules", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rulesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jwuthri/Tracely-ai maintain-greptile-rules --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jwuthri/Tracely-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/maintain-greptile-rules .agents/skills/maintain-greptile-rules && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-greptile-rules" agent skill from https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rules into .agents/skills/maintain-greptile-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-greptile-rules", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jwuthri/Tracely-ai maintain-greptile-rules --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jwuthri/Tracely-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/maintain-greptile-rules .cursor/skills/maintain-greptile-rules && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maintain-greptile-rules" agent skill from https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rules into .cursor/skills/maintain-greptile-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-greptile-rules", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jwuthri/Tracely-ai.git --path .claude/skills/maintain-greptile-rules--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jwuthri/Tracely-ai maintain-greptile-rules --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jwuthri/Tracely-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/maintain-greptile-rules .gemini/skills/maintain-greptile-rules && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maintain-greptile-rules" agent skill from https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rules into .gemini/skills/maintain-greptile-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-greptile-rules", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jwuthri/Tracely-ai maintain-greptile-rulesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jwuthri/Tracely-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/maintain-greptile-rules .github/skills/maintain-greptile-rules && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maintain-greptile-rules" agent skill from https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rules into .github/skills/maintain-greptile-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-greptile-rules", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jwuthri/Tracely-ai maintain-greptile-rules --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jwuthri/Tracely-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/maintain-greptile-rules .opencode/skills/maintain-greptile-rules && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maintain-greptile-rules" agent skill from https://github.com/Jwuthri/Tracely-ai/tree/master/.claude/skills/maintain-greptile-rules into .opencode/skills/maintain-greptile-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-greptile-rules", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
maintain-greptile-rules- GitHub stars
- 1.5k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 498 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Evaluate verified findings from merge-ready, Greptile, pull-request, CI, security, billing, and other code reviews, then promote durable review gaps into the version-controlled .greptile…
- Works in 5 steps: Verify the finding → Route it to the right mechanism → Apply the promotion bar → …
- A review uncovers a recurring
- SKILL.md covers 1. Verify the finding, 2. Route it to the right…, 3. Apply the promotion bar and 4. Edit conservatively, plus 1 more section
- Calls jq, prettier and git
What it does
Maintain Greptile Rules is an agent skill from Jwuthri/Tracely-ai. Evaluate verified findings from merge-ready, Greptile, pull-request, CI, security, billing, and other code reviews, then promote durable review gaps into the version-controlled .greptile configuration. Use when a review uncovers a recurring or high-risk repository invariant that Greptile does not capture, when Greptile repeatedly produces a false positive, or when asked to audit or update OpenSEO's Greptile rules and context.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Code review, LLM evaluation and Pull requests. The repository describes itself as: Trace-native CI/CD for AI agents — production failures become regression tests that block the PR. Auto-detect, cluster, freeze into hermetic cases, replay in CI for $0. The licence is MIT.
When your agent uses it
- A review uncovers a recurring
- High-risk repository invariant that Greptile does not capture
- Greptile repeatedly produces a false positive
- Update OpenSEOs Greptile rules and context
Example prompts
- “/maintain-greptile-rules”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Verify the finding
- Route it to the right mechanism
- Apply the promotion bar
- Edit conservatively
- Validate
What it can do on your machine
Read from SKILL.md and the folder at commit 2962e1b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jqprettiergit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Maintain Greptile Rules loads about 1.1k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 498 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
GitHub didn't answer just now, so the file isn't shown here. It has 498 words (~1,088 tokens).
- name
- maintain-greptile-rules
- metadata.internal
- true
Files
SKILL.md and 1 other file in .claude/skills/maintain-greptile-rules of Jwuthri/Tracely-ai.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2962e1b
Compare with similar skills
Maintain Greptile Rules next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Maintain Greptile Rules this skillJwuthri/Tracely-ai | 1.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Open Code Review CLIalibaba/open-code-review | 45k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
- Official
GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Code Review
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
More from Jwuthri/Tracely-ai
AI Observability Langchain Python
Jwuthri/Tracely-ai
PostHog AI Observability integration for LangChain (Python). An agent skill from Jwuthri/Tracely-ai.
Openseo Review Web Content
Jwuthri/Tracely-ai
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs.
SEO Audit
Jwuthri/Tracely-ai
Audit a website and deliver a one-page, plain-language SEO report anyone can act on, centered on a single do-this-week action.
Related
Categories
Questions about Maintain Greptile Rules
What does Maintain Greptile Rules do?
Evaluate verified findings from merge-ready, Greptile, pull-request, CI, security, billing, and other code reviews, then promote durable review gaps into the version-controlled .greptile…. Maintain Greptile Rules is an agent skill from Jwuthri/Tracely-ai.greptile configuration.
When should I use Maintain Greptile Rules?
Maintain Greptile Rules fits situations like: A review uncovers a recurring; high-risk repository invariant that Greptile does not capture; greptile repeatedly produces a false positive; update OpenSEOs Greptile rules and context.
How do I install Maintain Greptile Rules in Claude Code?
Run `npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a claude-code`. Or copy the skill folder (.claude/skills/maintain-greptile-rules in Jwuthri/Tracely-ai) into .claude/skills/maintain-greptile-rules in your project. Claude Code loads it when a task matches its description.
How do I install Maintain Greptile Rules in Codex?
Run `npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a codex`. Or copy the skill folder (.claude/skills/maintain-greptile-rules in Jwuthri/Tracely-ai) into .agents/skills/maintain-greptile-rules in your project. Codex loads it when a task matches its description.
Can I use Maintain Greptile Rules in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jwuthri/Tracely-ai --skill maintain-greptile-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-greptile-rules, .gemini/skills/maintain-greptile-rules, .github/skills/maintain-greptile-rules and .opencode/skills/maintain-greptile-rules in your project.
What does Maintain Greptile Rules need to run?
Going by SKILL.md and its folder, Maintain Greptile Rules needs the command-line tools its instructions call (jq, prettier and git).
Does Maintain Greptile Rules access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Maintain Greptile Rules safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Maintain Greptile Rules use?
Maintain Greptile Rules is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maintain Greptile Rules use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Maintain Greptile Rules?
Skills that share tags, products or a category with Maintain Greptile Rules: PR Babysitter (openinterpreter/openinterpreter, 69k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Open Code Review CLI (alibaba/open-code-review, 45k stars) and GitHub Review Iteration (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain Greptile Rules?
Jwuthri (a GitHub user) maintains it in Jwuthri/Tracely-ai, which has 1,535 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: Jwuthri/Tracely-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.