Lets Start Skill

/lets-start

A Claude Code and Codex skill that starts every session in the right place. `/lets-start` asks what you're building, installs [gstack](https://github.com/garrytan/gstack) if missing, sets up an isolated feature branch and worktree, checks host-specific session conventions, and routes you to the gstack or companion skill that fits the task.

The bundle also ships `/audit-tests`, `/tidy-code`, `/autoclean`, `/parallelize`, and `/ship-then-deploy` for pre-release cleanup, test coverage, parallel work, and release passes.

Install

Claude Code

Paste this prompt into Claude Code:

Install the /lets-start skill for Claude Code: `git clone https://github.com/ashrust/lets-start-skill.git ~/.claude/skills/lets-start-skill && cd ~/.claude/skills/lets-start-skill && bash setup.sh --host claude`

Then type `/lets-start` to kick off your first session.

Codex

Paste this prompt into Codex:

Install the /lets-start skill for Codex: `git clone https://github.com/ashrust/lets-start-skill.git ~/.codex/skills/lets-start-skill && cd ~/.codex/skills/lets-start-skill && bash setup.sh --host codex`

Then start a new Codex session or reload skills if needed, and invoke `/lets-start`.

Upgrading from a single-skill install

Earlier versions cloned directly into `~/.claude/skills/lets-start`. If you have that layout (a real git repo at that path, not a symlink), remove it before installing the new layout. Codex users should do the same check for `~/.codex/skills/lets-start`. If setup reports that `SKILL.md` is a real file, move that legacy file aside after checking there is nothing custom you need.

Claude Code prompt:

Check `~/.claude/skills/lets-start` for unpushed commits or uncommitted changes. If it is clean, or already a symlink, remove it with `rm -rf ~/.claude/skills/lets-start`. Then install the new layout: `git clone https://github.com/ashrust/lets-start-skill.git ~/.claude/skills/lets-start-skill && cd ~/.claude/skills/lets-start-skill && bash