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 para a instalação

Repositório: sneivandt/install-arch
Última atividade na origem: 15 de agosto de 2026 às 18:58
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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 todas deste repositório

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.