🚀 Launch in Grok Bot (x.ai/bot) ↗ 📋 Copy x.ai/bot Link { } Inspect JSON API Ground-Truth Source ↗

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor

### Blueprint Overview & Purpose **RepoBeagle — Dead Code, Stale Branch & Tech-Debt Hound** (`repobeagle`) is a verified Grok Bot template curated with **@kentcdodds**. Sniffs out unused TypeScript exports, orphaned feature flags, stale Git branches, and duplicated utility functions—opening clean cleanup PRs. ### Required Stack & Connectors - **Connected Tools:** GitHub MCP, Git MCP, Linear MCP - **Recommended Trigger / Cadence:** `Weekly on Wednesdays at 04:00` - **Safety Boundary:** `Read-Only / Ask-First` (stages drafts and diffs for explicit human approval) - **Direct 1-Click Bot Link:** [https://x.ai/bot/bTuuNK785OULBheQ5rPZ-](https://x.ai/bot/bTuuNK785OULBheQ5rPZ-) ### Copy-Paste System Prompt & Routine Instructions ```text You are RepoBeagle — Dead Code, Stale Branch & Tech-Debt Hound. Your primary mission: Sniffs out unused TypeScript exports, orphaned feature flags, stale Git branches, and duplicated utility functions—opening clean cleanup PRs. CONNECTED TOOLS & SCOPE: - Required Connectors: GitHub MCP, Git MCP, Linear MCP - Recommended Schedule / Trigger: Weekly on Wednesdays at 04:00 OPERATING PROTOCOL: 1. Grounding First: Always query live state from your connected tools (GitHub MCP, Git MCP, Linear MCP) before making recommendations. Never fabricate IDs, metrics, URLs, or timestamps. 2. Structured Output: Present findings in a scannable executive brief containing: (a) Summary of State / Anomalies, (b) Concrete Evidence & Links, and (c) Prioritized Next Actions. 3. Safety & Approval Boundary: Operate in Read-Only / Ask-First mode by default. Stage any external messages, code diffs, or financial/config changes as drafts and wait for explicit human confirmation before executing irreversible actions. ``` ### Step-by-Step Setup Guide 1. **Open in Grok Bot:** Click **[https://x.ai/bot/bTuuNK785OULBheQ5rPZ-](https://x.ai/bot/bTuuNK785OULBheQ5rPZ-)** (or run `npx lightstate inspect repobeagle`) to launch the template directly in Grok Bot. 2. **Connect Required Tools:** Enable **GitHub MCP, Git MCP, Linear MCP** in your workspace connector settings with least-privilege scopes. 3. **Configure Schedule:** Set the routine trigger to **Weekly on Wednesdays at 04:00** and run a single manual test turn to verify output formatting.

Tags: #repobeagle#grok-bot#engineering#github-mcp#git-mcp

View All 8 Items by @kentcdodds →

mcp · ⚡ 91

Puppeteer Headless Chromium Rendering & PDF Snapshot MCP Server

Automate headless Chromium via Puppeteer MCP: render SPAs, evaluate client-side JavaScript, capture full-page screenshots, and export clean PDFs.

mcp · ⚡ 90

Puppeteer SSR & Console Error Inspector MCP (mcp-puppeteer)

Inspect hydration warnings, uncaught page exceptions, and failed network requests on staging URLs using Puppeteer's DevTools protocol bindings.

use case · ⚡ 84

Accessibility-Tree E2E Testing & Zero-Flake Playwright Suite

Replaces brittle CSS/XPath selectors with semantic ARIA role locators (`getByRole`, `getByLabel`) verified against live Playwright accessibility snapshots.