How do I install the Start Rails Server skill?

Run npx skillmds@latest add willakins/start-rails-server in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Start Rails Server safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Start Rails Server?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Start Rails Server free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Start Rails Server?

willakins (@willakins) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Start Rails Server by willakins — Agent Skill

Name: Start Rails Server
Author: willakins

Start Rails Server

Start, reuse, stop, or report the local Rails development stack for the current worktree with separate terminals for Rails server, Tailwind watch, and Sidekiq, using a worktree-specific `.localhost` URL. Use when Codex needs to boot or stop the app locally, avoid port and browser-cookie collisions across multiple worktrees, or give the user the exact local URL for the running branch.

willakins d0735f4 4 files · 8.9 KB Updated Sep 17, 2026

File contents

Use this skill when the user asks for the app to be started or stopped locally, for example:

start the rails server
boot this branch locally
find an open port and run the app
give me the local URL for this worktree
stop the local Rails server

Goal

Start exactly one local development stack for the current worktree and return a reachable worktree-specific .localhost URL.

Read parallel Rails details for command variants, launcher behavior, failure handling, and output rules.

Workflow

Run parallel rails s from the target Rails app root.
Let it attach a Zellij session when available, with a prominent working shell plus smaller selectable service panes for:
- bin/rails server
- bin/rails tailwindcss:watch
- bundle exec sidekiq
Let it pick the next free port starting at 3000 when no port is specified.
Return the URL printed on stdout. Use that URL instead of localhost:<port> so each worktree gets separate browser cookies.

Command

Run from the target Rails repo root:

parallel rails s

If the user explicitly wants a specific port, pass it as a bare argument or with --port:

parallel rails s 3107
parallel rails s --port 3107

Stop the three terminals for the current worktree:

parallel rails s stop

Check whether the stack is tracked as running:

parallel rails s status

If the user explicitly wants a URL host, pass it through:

parallel rails s --hostname backburner-3.localhost

Behavior

Treat the current working directory as the target worktree.
Require bin/rails to exist in that directory.
Refuse to start a duplicate stack when tracked terminals are already running for the same worktree.
Start Rails in development and bind it to 127.0.0.1.
Return http://<worktree-name>.localhost:<port> by default, sanitized as a DNS label.
Keep browser sessions isolated across worktrees by avoiding shared localhost cookies.
Print only the final URL on success so the caller can relay it directly.

---name: start-rails-serverdescription: Start, reuse, stop, or report the local Rails development stack for the current worktree with separate terminals for Rails server, Tailwind watch, and Sidekiq, using a worktree-specific `.localhost` URL. Use when Codex needs to boot or stop the app locally, avoid port and browser-cookie collisions across multiple worktrees, or give the user the exact local URL for the running branch.---Use this skill when the user asks for the app to be started or stopped locally, for example:- `start the rails server`- `boot this branch locally`- `find an open port and run the app`- `give me the local URL for this worktree`- `stop the local Rails server`## GoalStart exactly one local development stack for the current worktree and return a reachable worktree-specific `.localhost` URL.Read [parallel Rails details](references/parallel-rails.md) for command variants, launcher behavior, failure handling, and output rules.## Workflow1. Run `parallel rails s` from the target Rails app root.2. Let it attach a Zellij session when available, with a prominent working shell plus smaller selectable service panes for: - `bin/rails server` - `bin/rails tailwindcss:watch` - `bundle exec sidekiq`3. Let it pick the next free port starting at `3000` when no port is specified.4. Return the URL printed on stdout. Use that URL instead of `localhost:<port>` so each worktree gets separate browser cookies.## CommandRun from the target Rails repo root:```bashparallel rails s```If the user explicitly wants a specific port, pass it as a bare argument or with `--port`:```bashparallel rails s 3107parallel rails s --port 3107```Stop the three terminals for the current worktree:```bashparallel rails s stop```Check whether the stack is tracked as running:```bashparallel rails s status```If the user explicitly wants a URL host, pass it through:```bashparallel rails s --hostname backburner-3.localhost```## Behavior- Treat the current working directory as the target worktree.- Require `bin/rails` to exist in that directory.- Refuse to start a duplicate stack when tracked terminals are already running for the same worktree.- Start Rails in `development` and bind it to `127.0.0.1`.- Return `http://<worktree-name>.localhost:<port>` by default, sanitized as a DNS label.- Keep browser sessions isolated across worktrees by avoiding shared `localhost` cookies.- Print only the final URL on success so the caller can relay it directly.

Frequently asked questions