hello
/hello
Start a working session. Read where the last one stopped, bring the project and its setup to the latest state, clear finished work, and say what to do next. Use when someone says "hello", "hi", "good morning", "let's start", "let's get going", "where were we", "what's next", or at the start of a session when the start-of-session note says to say hello.
- Author
- solidvibes ↗
- Repository
- solid-vibes ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Start a working session. Read where the last one stopped, bring the project and its setup to the latest state, clear finished work, and say what to do next. Use when someone says "hello", "hi", "good morning", "let's start", "let's get going", "where were we", "what's next", or at the start of a session when the start-of-session note says to say hello.
Triggers from the description
Original author description
Start a working session. Read where the last one stopped, bring the project and its setup to the latest state, clear finished work, and say what to do next. Use when someone says "hello", "hi", "good morning", "let's start", "let's get going", "where were we", "what's next", or at the start of a session when the start-of-session note says to say hello.
How it works
- 1. Read the status
- 2. Pick up the handover
- 3. Bring the project to its latest state
- 4. Clear finished work
- 5. Stack checks
- 6. Brief
SKILL.md preview
--- name: hello description: Start a working session. Read where the last one stopped, bring the project and its setup to the latest state, clear finished work, and say what to do next. Use when someone says "hello", "hi", "good morning", "let's start", "let's get going", "where were we", "what's next", or at the start of a session when the start-of-session note says to say hello. --- # Hello The start of a session, kept light. It picks up where the last one stopped, so nothing is lost overnight or to a compacted conversation, brings the project to its latest state and says what to do next. It never upgrades packages or tools and never audits; that is the `update` skill, run now and then. How you talk to the user: - Plain words, outcomes only. Say what you are about to do before you do it. - Short. One line per thing found; details only when something needs their answer. - One round at a time; group related questions. The `solidvibes` command: in Claude Code the plugin puts it on the path; elsewhere it is `bin/solidvibes` in the Solid Vibes folder, two levels above this file's folder. ## 1. Read the status From the repo root, run `git fetch` (no remote: skip it), then `solidvibes hello --full`. It prints one line each: - `handover`: whether `.solidvibes/handover.md` exists, and its age; - `setup`: `same` or `differs`, the project's Solid Vibes and profile versions against the installed ones; then `solidvibes doctor` (the project's setup health) and `solidvibes worktrees` (finished side copies of the project). The `ci` and `docs` lines are for `update`; skip them here. No Factory contract in `AGENTS.md`, or `setup: none`: say so in plain words and offer the `interview` skill. Stop here unless they decline. ## 2. Pick up the handover Read `.solidvibes/handover.md` if it exists: Done, Open, Next, and the `## Snapshot` (branch, uncommitted work, last commits) written before the last compaction. Keep it in mind for the brief. Don't recite it. ## 3. Bring the project to its latest state - **Latest commits.** When the current branch has an upstream and is behind it: with no uncommitted work, `git pull --ff-only` and say how many commits came in. Uncommitted work, or the branch has its own commits too: say so in one line and leave it. Never stash, merge or rebase here. - **Latest setup.** On `setup: differs`, say "Solid Vibes was updated since this project was set up; I'll bring its files up to date. Nothing you wrote changes." Then follow `../interview/setup.md` (next to the `interview` skill) as a refresh: profile and agents from `.solidvibes/manifest.json`, never the blank defaults. Report what it changed in one line. - **Doctor problems**: say each in one plain line and offer the fix; fix only on a yes. Never update Solid Vibes itself here; Claude Code updates the plugin, and other agents rerun `solidvibes install`. ## 4. Clear finished work When the worktrees table has rows marked `remove`, say "I'll clear N finished side copies of the project; nothing unfinished is touched." Then run `solidvibes worktrees --clean <repo root>`, always with the repo root, never a folder of projects. Report what was freed in one line. ## 5. Stack checks Run what `## Checks at hello` in `docs/stack.md` lists, and say each result in one line. A failing check: say what it means and offer to fix it. Missing section, or still the italic placeholder: skip it; `update` drafts it. When `## Packs` in `docs/stack.md` lists `linear`, also run the `linear` pack's `## At hello`; its lines go in the brief. ## 6. Brief One short message, a few lines: - **Done in this hello**: what came in, what was refreshed or cleared. Nothing: leave the line out. - **Needs you**: anything waiting on the user (a doctor problem, a failing check, an owner check from the handover's Open). - **Now**: the handover's Next, then plans in the contract's `plans` folder with `status: not-started` or `draft`, newest first. - **Ideas**: only when Now is empty, the parked ideas in `docs/ideas/`, one line each from its first sentence. End with a question about what to work on, the first Now item (or, with none, the first idea) as the suggestion.
Versions
The database has no other skills named hello.
Database snapshot: 13.11.2026 · package version 18d670741452 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86start-session
Begin a work session on this game. Use at the start of a conversation, after /clear, or when the user says "let's get going", "where were we", or "what's next". Loads HANDOFF and ROADMAP, checks git state, runs a quick health check, and proposes the first task. - 90session-start
Start a work session from the handoff the previous one left in `.gemba/sessions`: read the latest handoff, check it against Jira and the code, and propose its next step as one option. Use when someone says "retoma la sesión", "continúa donde quedamos", "session start" or "qué… - 100work-start
Initialize a new task with proper context loading and archive setup. Use when starting fresh work on a feature, bug fix, or project. - 90prod-good-morning
Morning orientation that recaps recent work, checks agenda, emails, meetings and tasks, then helps decide what to work on. Trigger when user says 'good morning', 'morning', 'start my day', 'what do I have today', or anything that signals beginning of a work session. Use it… - 100cursor-hello-world
Create your first project with Cursor AI features. Triggers on "cursor hello world", "first cursor project", "cursor getting started", "try cursor ai", "cursor basics". Use when working with cursor hello world functionality. Trigger with phrases like "cursor hello world", "cursor world", "cursor". - 100open
Boot a session, load vault context, and surface what matters. Use when opening a session, saying good morning, or starting work.