From claude-code-facilito
Sincronizar el repo y empezar a trabajar en algo nuevo
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-code-facilito:arrancar [qué vas a hacer]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /arrancar — Preparar todo para empezar a trabajar This command helps a non-technical user sync their repo, set up local dev, and start working. Communicate ALWAYS in casual Colombian Spanish (use "parce", "listo", "dale", "tranqui" naturally). Keep messages short, friendly, and non-technical. NEVER show raw git/npm output — translate everything to simple language. ## First: Create task list for progress tracking ALWAYS create tasks using TaskCreate so the user sees progress in the status line. Create these tasks immediately: 1. "Revisar estado del repo" (activeForm: "Revisando el repo...
This command helps a non-technical user sync their repo, set up local dev, and start working. Communicate ALWAYS in casual Colombian Spanish (use "parce", "listo", "dale", "tranqui" naturally). Keep messages short, friendly, and non-technical. NEVER show raw git/npm output — translate everything to simple language.
ALWAYS create tasks using TaskCreate so the user sees progress in the status line. Create these tasks immediately:
Mark each task in_progress BEFORE starting it, and completed when done.
Mark task 1 as in_progress.
Run git status --porcelain to check for uncommitted changes.
If there are uncommitted changes: Use AskUserQuestion to ask:
git stash push -m "cambios-guardados-$(date +%Y%m%d)" or commit to temp branchgit checkout -- . && git clean -fdIf clean: Continue silently.
Also check current branch. If on a feature branch (not main), use AskUserQuestion:
Mark task 1 as completed.
Mark task 2 as in_progress.
git checkout main
git pull --rebase origin main
If pull fails due to conflicts:
"Hay unos cambios que chocan. Voy a arreglarlo, tranqui."
Try git rebase --abort and then git pull origin main (merge fallback). If still fails, explain simply and use AskUserQuestion to offer options.
Also run npm install if package-lock.json changed (check with git diff HEAD@{1} --name-only | grep package-lock).
Mark task 2 as completed.
Mark task 3 as in_progress.
If $ARGUMENTS is provided, use that as the description. Otherwise use AskUserQuestion:
From the user's choice, generate a branch name:
fix/<short-kebab-case>feat/<short-kebab-case>chore/<short-kebab-case>feat/ if unclearIf user typed a custom description, derive the branch name from it.
git checkout -b <type>/<short-kebab-case-description>
Mark task 3 as completed.
Mark task 4 as in_progress.
Check if dependencies are installed:
ls node_modules/.package-lock.json 2>/dev/null
If not installed, run npm install and tell the user:
"Instalando lo que necesita la app... un momentico."
Then use AskUserQuestion to ask what they want to do:
If yes, start the dev server:
npm run dev
Tell the user:
"La app está corriendo en tu computador. Abre el navegador en la dirección que aparece arriba para verla."
Explain briefly about environments:
"📝 Dato útil: Hay tres versiones de la app:" "- Tu computador — lo que ves ahorita, solo tú lo ves" "- Vista previa — cuando hagas
/listo, Vercel crea una versión de prueba online" "- La oficial — cuando Jairo apruebe, se publica automáticamente en laolibero.com"
Mark task 4 as completed.
Print a friendly confirmation:
"¡Listo parce! 🚀 Ya estás en la rama
<branch>con todo actualizado." "" "Trabaja tranqui y cuando termines, escribe/listoy yo me encargo del resto."
Do NOT show any git commands or technical details to the user.
npx claudepluginhub jairotorregrosa/claude-code-facilito --plugin claude-code-facilito