Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

remove-app

Estrelas4

Forks0

Atualizado8 de maio de 2026 às 11:09

Removes an application from NixOS or Home Manager configuration. Locates all references, assesses impact on shared modules, and safely removes.

Instalação

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ê.

Executar no Manus

Fonte

Hayao0819

Hayao0819/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	remove-app
description	Removes an application from NixOS or Home Manager configuration. Locates all references, assesses impact on shared modules, and safely removes.
when_to_use	When the user asks to remove, uninstall, or delete an application or package from their Nix configuration.
argument-hint	<app-name>
allowed-tools	WebSearch, WebFetch(domain:mynixos.com), Bash(nix search:), Bash(nix flake check:), Read, Edit, Write, Glob, Grep, AskUserQuestion

Remove Application: $ARGUMENTS

1. Locate

Use Grep to find all references to the package across .nix files:

nixos/*/configuration.nix — System packages
modules/nixos/*/default.nix — NixOS modules
modules/home-manager/*/default.nix — Home Manager modules
modules/home-manager/pkgs/global.nix — Cross-platform CLI
modules/home-manager/pkgs/linux.nix — Linux-only CLI

2. Assess Impact

Single location: Safe to remove directly
Shared module: Ask the user — the module may be used by multiple systems
Dependency: Inform the user if removing it would break another package

3. Remove

Remove the package/configuration
If the app had its own module directory, delete it (auto-import handles the rest)
Clean up related config (environment variables, services, etc.)

4. Validate

nix flake check --extra-experimental-features 'nix-command flakes pipe-operators'

Mais deste repositório

mesmo repositório

writing-tech-article

Hayao0819/dotfiles

Drafts fact-based technical articles for hayao's outlets — Zenn (@hayao), Qiita (@Hayao0819), the personal blog (hayao0819.com) — matching his structural register without faking his personality. Use when writing, drafting, or rewriting a 技術記事 / blog post / Zenn / Qiita article in hayao's name about a technical topic. The LLM writes facts only: it does NOT manufacture his jokes, 毒舌, 自虐, casual throwaway closers, or first-person anecdotes — performing his personality is fabrication and he finds it offensive. Encodes the factual baseline of his writing (genre-driven 敬体/常体, direct openings, plain content-label headings, inline-code density, primary-source links) in a bundled reference.md, and composes with the natural-writing skill. Self-contained — does not depend on machine-local memory. Do NOT use for: non-hayao docs, pure code, commit messages, or chat replies.

2026-06-264

natural-writing

Hayao0819/dotfiles

Rewrites prose so it reads as if a human wrote it — stripping out LLM tells in both English and Japanese. Use whenever producing user-visible writing of any kind: documentation, README, markdown, blog posts, commit messages, PR descriptions, GitHub Issues, code-review comments, code comments and docstrings, replies in issue threads, professional or casual emails, Slack/Discord/chat messages, release notes, design docs, academic-style writeups and 論文. Use it even when the user did not ask for "natural" prose — any drafted text leaving Claude that a human will read should pass through this checklist first. Triggers include: any request to "write", "draft", "compose", "summarize", "explain", "describe", "review", "comment", "reply", or 「書いて」「文章作って」「まとめて」「メール作って」「返信して」「PR/Issueの説明書いて」. Do NOT use for: pure code generation with no prose, raw data transformations, or terse tool output.

2026-06-254

auditing-c-memory

Hayao0819/dotfiles

Security audit of memory-safety vulnerabilities in C/C++ (userland/systems, not kernel), with confidence-gated reporting to keep false positives low. Taint-traces untrusted input (argv, env, files, network, stdin) to memory sinks (copy length, array index, allocation size, format string) and reports only when input is attacker-controlled AND reaches the sink AND bounds aren't enforced. Covers buffer overflow, use-after-free, double-free, OOB read, integer overflow into undersized alloc, format string, the dangerous-function table, hardening flags to verify, and the ASan/UBSan/MSan/fuzzing toolchain. Covers userland/systems C and the SGX enclave/host (ECALL/OCALL) pointer boundary. Use when reviewing C/C++ for memory-corruption bugs. Kernel code → auditing-kernel.

2026-06-224

auditing-kernel

Hayao0819/dotfiles

Security audit of Linux kernel code and out-of-tree modules/drivers, with confidence-gated reporting to keep false positives low. Traces attacker input from userspace entry points (syscalls, ioctl, sysfs/proc/debugfs writes, netlink, char-dev, mmap) — and, for confidential-computing guests, from the untrusted host — to memory/refcount/locking/infoleak sinks. Covers UAF via refcount imbalance, the copy_to/from_user boundary, double-fetch TOCTOU, missing capability checks, integer-overflow allocations, ioctl handler review, and the TDX/SEV-SNP/SGX threat model. Use when reviewing kernel C, a driver/ LKM, an ioctl handler, or enclave/attestation code for vulnerabilities.

2026-06-224

auditing-web-app

Hayao0819/dotfiles

Security audit of web applications — backend implementation and authentication/ authorization flows — with confidence-gated reporting to keep false positives low. Traces attacker-controlled request input (params, body, headers, cookies, path) to sinks, distinguishing server-controlled from attacker-controlled, and reports HIGH only. Leads with broken access control / IDOR (OWASP #1), then injection (and where GORM/sqlc/React are already safe), XSS, SSRF, CSRF, auth (password storage, sessions, reset), and tokens (JWT alg confusion, OAuth/OIDC PKCE). Framework-aware for Go/Gin/GORM/sqlc and Next.js Server Actions. Use when reviewing a web backend, API, route handler, Server Action, or auth flow.

2026-06-224

writing-go

Hayao0819/dotfiles

Idiomatic, version-current Go review and authoring for an experienced engineer. Covers deliberate error wrapping (errors.Is/As/Join, AsType), structured concurrency (errgroup, context, the loopvar fix), modern stdlib that replaced old patterns (slices/maps/cmp, log/slog, min/max/clear, range-over-func iterators), table-driven and synctest testing, API design the linter can't check, and Gin/GORM/cobra backend patterns. Use when writing, reviewing, or refactoring Go — .go files, go.mod, goroutines, errors.Is/As, a Go backend or CLI — or before committing Go. Flags outdated pre-1.22 idioms (loopvar v:=v shadows, tools.go, hand-rolled helpers).

2026-06-224

name	remove-app
description	Removes an application from NixOS or Home Manager configuration. Locates all references, assesses impact on shared modules, and safely removes.
when_to_use	When the user asks to remove, uninstall, or delete an application or package from their Nix configuration.
argument-hint	<app-name>
allowed-tools	WebSearch, WebFetch(domain:mynixos.com), Bash(nix search:), Bash(nix flake check:), Read, Edit, Write, Glob, Grep, AskUserQuestion

Remove Application: $ARGUMENTS

1. Locate

Use Grep to find all references to the package across .nix files:

nixos/*/configuration.nix — System packages
modules/nixos/*/default.nix — NixOS modules
modules/home-manager/*/default.nix — Home Manager modules
modules/home-manager/pkgs/global.nix — Cross-platform CLI
modules/home-manager/pkgs/linux.nix — Linux-only CLI

2. Assess Impact

Single location: Safe to remove directly
Shared module: Ask the user — the module may be used by multiple systems
Dependency: Inform the user if removing it would break another package

3. Remove

Remove the package/configuration
If the app had its own module directory, delete it (auto-import handles the rest)
Clean up related config (environment variables, services, etc.)

4. Validate

nix flake check --extra-experimental-features 'nix-command flakes pipe-operators'