update
Use whenever the user wants to update - checks for new prompts from the instructor and runs them, then offers to customize the student's setup
Datos de origen
- Repositorio
- blakesims/cca
- Última actividad en el origen
- 3 de abril de 2026 a las 05:49
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 1
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- update
- description
- Use whenever the user wants to update - checks for new prompts from the instructor and runs them, then offers to customize the student's setup
# Update
## Process
1. Read `.completed` in this directory (create it if missing). This lists prompt filenames already run, one per line.
2. List all files in `prompts/todo/`. Check each against `.completed`.
3. If there ARE pending prompts:
- Tell the student how many updates are pending.
- Run them in numeric order (001 before 002, etc).
- After each completes, append its filename to `.completed`.
- Summarize what was done.
4. If `changelog.md` has entries newer than `.local-version`, show what changed in plain English.
5. Update `.local-version` to match `version.txt`.
6. If there are NO pending prompts (or after running them):
- Tell the student they're up to date, show version from `version.txt`.
- Ask: "Want to customize anything?" and suggest:
- Add or remove commands from your help sheet
- Change your command name
- Add a shell alias
- Ask anything about the terminal
- If they want to edit help.sh, read it first, make changes, test.
- If they rename their command, update the function in their rc file and re-source.
Ver en GitHub