ce-polish-beta

Starts a dev server, opens the feature in a browser, and iterates on fixes.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill ce-polish-beta-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-polish-beta
Source: https://github.com/mmnavarr/harness/tree/main/skills/ce-polish-beta
Command: npx skills add https://github.com/mmnavarr/harness --skill ce-polish-beta-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) components.

What problem does it solve? Manually figuring out how to start a project's dev server, which port it binds to, and how to open it in the right browser interrupts the flow of reviewing and polishing a feature branch. This Skill automates that setup so you can go straight from a branch or PR to a running, browsable feature and iterate on improvements conversationally. ## Core Features & Use Cases - Automatic dev-server startup: Reads .claude/launch.json when present, or auto-detects the project type (Rails, Next.js, Vite, Nuxt, Astro, Remix, SvelteKit, Procfile) including monorepo layouts, then resolves the package manager and port. - IDE-aware browser handoff: Detects Claude Code, Cursor, or VS Code via environment variables and opens the running feature in the appropriate browser mechanism. - Conversational iteration loop: You browse the feature, describe what feels off, and fixes are applied with hot-reload until you are done, at which point changes are committed. - Use Case: You check out a colleague's PR branch, invoke the skill, and within seconds the Next.js app is running on port 3000 in your browser; you say "the header spacing feels cramped" and the fix lands immediately. ## Quick Start Ask the AI to polish the current branch or a specific PR number so it starts the dev server and opens the feature in a browser for review.

Frequently Asked Questions about ce-polish-beta

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a dev server automatically for any framework?▼

Run the skill with a PR number, branch name, or blank for the current branch. It detects the project type from signature files like next.config.js or Gemfile, resolves the package manager from lockfiles, and starts the correct dev command in the background.

How is the dev server port resolved?▼

Port resolution follows a cascade: explicit flag, framework config files, puma.rb, Procfile.dev, docker-compose.yml, package.json scripts, .env files, then framework defaults (3000 for Rails/Next, 5173 for Vite/SvelteKit, 4321 for Astro).

Does it work with monorepos?▼

Yes. When no framework signature is found at the repo root, a probe searches subdirectories up to depth 3 and emits type@directory hits such as next@apps/web. Multiple hits trigger a disambiguation prompt.

Can I use a custom start command instead of auto-detection?▼

Yes. Create a .claude/launch.json file at the repo root with runtimeExecutable, runtimeArgs, and port fields. The skill reads it first and skips auto-detection entirely when a valid configuration exists.

Which IDEs support the browser handoff?▼

Claude Code, Cursor, and VS Code are detected via environment variables like CLAUDE_CODE, CURSOR_TRACE_ID, and TERM_PROGRAM. If detection fails, the URL is printed so you can open it manually in any browser.