ce-polish-beta

Start a dev server, open the feature in a browser, and iterate on fixes conversationally.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-polish-beta-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-polish-beta
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-polish-beta
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-polish-beta-norfolk-group

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 a browser interrupts the flow of reviewing and polishing a feature branch. This Skill automates that setup so you can focus on using the feature and describing what to fix. ## Core Features & Use Cases - Automatic dev-server startup: Detects the project type (Rails, Next.js, Vite, Nuxt, Astro, Remix, SvelteKit, or Procfile-based) from signature files, resolves the package manager from lockfiles, and starts the correct dev command. - Port resolution cascade: Probes framework configs, Procfile.dev, docker-compose.yml, package.json scripts, and .env files to find the actual port, falling back to framework defaults. - launch.json support: Reads .claude/launch.json for user-defined start configurations and can write a stub for your detected framework. - IDE browser handoff: Detects Claude Code, Cursor, or VS Code via environment variables and opens the running app in the appropriate embedded browser. - Use Case: You check out a colleague's PR branch, invoke the skill, and within seconds the dev server is running in your browser. You click through the feature, say "the submit button feels misaligned on mobile," and the fix is applied and hot-reloaded. ## Quick Start Ask the assistant to polish the current branch or a specific PR number, then browse the running feature and describe what to improve.

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 polish skill on your branch and it detects the project type from signature files like next.config.js or vite.config.ts, resolves the package manager from lockfiles, and starts the correct dev command. It then probes localhost until the server responds.

How does the skill detect which port my dev server uses?

Port resolution follows a cascade: explicit flag, framework config files, config/puma.rb, Procfile.dev web line, docker-compose.yml, package.json scripts, then .env files. If nothing matches, it falls back to framework defaults like 3000 for Rails or 5173 for Vite.

Does it work with monorepos like Turborepo or pnpm workspaces?

Yes. When no framework signature exists at the repo root, the script probes subdirectories up to depth 3 for config files and reports hits like next@apps/web. For multiple hits it asks you to disambiguate, and launch.json supports a cwd field.

Can I define my own dev server start command?

Yes. Create a .claude/launch.json file at the repo root with runtimeExecutable, runtimeArgs, and port fields, following a subset of VS Code's launch.json schema. The skill reads it first and skips auto-detection entirely.

What happens if the dev server fails to start?

The skill probes http://localhost on the resolved port for up to 30 seconds. If the server does not come up, it shows the last 20 lines of the server log and asks you how to proceed rather than guessing.

Which frameworks are supported for auto-detection?

Auto-detection covers Rails, Next.js, Vite, Nuxt, Astro, classic Remix, SvelteKit, and Procfile-based projects. Remix on Vite is detected as vite since it uses vite.config.ts, and unknown project types prompt you for the start command.