arch-installer-maintenance

Use when adding installer features, changing package lists, working with dialog prompts, dotfiles integration, docs, project workflow, or other non-storage maintenance tasks.

Ir a la instalación

Repositorio: sneivandt/install-arch
Última actividad en el origen: 15 de agosto de 2026 a las 18:58
Idioma detectado de SKILL.md: inglés
Estrellas: 0
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.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/sneivandt/install-arch --skill arch-installer-maintenance

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

arch-installer-safety

Use when modifying install-arch.sh safety-sensitive behavior, including disk partitioning, encryption, LVM, chroot operations, bootloader/initramfs config, sudo, users, services, or cleanup.

2026-08-15

arch-installer-testing

Use when validating install-arch changes, updating tests, or working with dry-run, test-mode, ShellCheck, syntax checks, or loop-device integration tests.

2026-08-15

Ver todos los de este repositorio

Arch Installer Maintenance

Use this skill for routine feature work and repository maintenance that is not primarily disk/encryption/boot safety logic.

Feature and bug workflow

Read nearby patterns in install-arch.sh before editing.

Keep changes minimal, but complete across script, tests, docs, and CI.

Add or update tests when adding functions, changing package lists, device naming, prompts, dry-run output, or dotfiles flow.

Update README.md for user-visible behavior, paths, package sets, install modes, security posture, or troubleshooting changes.

Package and mode changes

Keep source package definitions in BASE_PACKAGES, GUI_PACKAGES, and VBOX_PACKAGES; runtime arrays may extend copies of those definitions.

Consider dotfiles-owned packages before adding installer-owned packages; avoid duplicating dotfiles AUR/package responsibilities.

Verify Arch package names; unit tests validate the production arrays directly.

Minimal mode uses the base dotfiles profile. Workstation and VirtualBox use the desktop profile.

Dotfiles integration

Clone dotfiles to /home/$user/src/dotfiles.

Run dotfiles as the target user through as_user.

Validate with dotfiles.sh test -p <profile> before running dotfiles.sh install -p <profile> -v.

Preserve HOME, USER, and LOGNAME when running dotfiles commands in the target system.

Dialog and input prompts

Capture dialog output with --stdout --clear and handle cancel/failure.

Validate prompt outputs immediately.

Keep prompt dimensions and labels readable in small terminals.

Documentation and workflow

Keep .github/pull_request_template.md, .github/workflows/ci.yml, and README.md aligned with actual script/test paths.

Follow conventional commit style when committing unless the user asks otherwise.

name	arch-installer-maintenance
description	Use when adding installer features, changing package lists, working with dialog prompts, dotfiles integration, docs, project workflow, or other non-storage maintenance tasks.