lets-polish-beta

Launches a development server and opens the app in-browser for real-time collaborative code review and iteration.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/williamzelesny/lets-engineer --skill lets-polish-beta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lets-polish-beta
Source: https://github.com/williamzelesny/lets-engineer/tree/main/plugins/lets-engineer/skills/lets-polish-beta
Command: npx skills add https://github.com/williamzelesny/lets-engineer --skill lets-polish-beta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The lets-polish-beta skill addresses the challenge of collaboratively reviewing and iterating on features in real time, reducing back-and-forth communication and streamlining the development process.

Core Features & Use Cases

  • Real-time Code Review: Collaboratively review code with the development team and iterate on features in real time.
  • Browser Integration: Open the feature in a browser directly from the codebase, allowing for live iteration and feedback.
  • Hot Reloading: Watch changes in real time as they are made and see the impact on the feature immediately.
  • Use Case: Ideal for when a feature is ready for review but needs fine-tuning before final implementation. Instead of discussing changes on a whiteboard or through email, the team can directly interact with the code in a browser, making real-time improvements.

Quick Start

/lets-polish-beta [PR number, branch name, or blank for current branch]

Frequently Asked Questions about lets-polish-beta

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

FAQPage Schema
How do I set up real-time code review for front-end web development?▼

Real-time code review for front-end web development involves starting a development server and opening a feature branch in a browser to collaboratively iterate and provide immediate feedback on live changes.

Does this hot reloading workflow support Vite and Next.js environments?▼

This hot reloading workflow supports Vite, Next.js, and Rails environments. It requires repository access and a supported development environment to watch real-time changes and iterate on features directly in the browser.

What is the best way to collaboratively iterate on a feature before final implementation?▼

The best way to collaboratively iterate before final implementation is to interact with the code directly in a browser using hot reloading, replacing whiteboard discussions or email threads with live, real-time improvements.

How do I start a dev server to review a specific pull request in the browser?▼

To start a dev server and review a specific pull request, you invoke the command with the PR number or branch name. This opens the feature in a browser for immediate testing and collaborative feedback.

When do I need browser integration for feature iteration?▼

You need browser integration for feature iteration when a feature is ready for review but requires fine-tuning. It allows the team to directly interact with the code and see the impact of changes immediately through hot reloading.