Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

cleanup

Étoiles4

Forks0

Mis à jour8 mai 2026 à 11:09

Performs comprehensive cleanup of the Nix codebase. Detects anti-patterns, removes dead code, fixes inconsistencies, and validates.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Hayao0819

Hayao0819/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	cleanup
description	Performs comprehensive cleanup of the Nix codebase. Detects anti-patterns, removes dead code, fixes inconsistencies, and validates.
when_to_use	When the user asks to clean up, lint, or improve the quality of their Nix configuration files.
allowed-tools	Read, Edit, Write, Glob, Grep, Bash(nix flake check:), Bash(nix eval:)

Nix Codebase Cleanup

Phase 1: Anti-Pattern Detection

Scan for and fix:

rec { } → Use let ... in instead (infinite recursion risk)
Top-level with → Use inherit or qualified names
Lookup paths <...> → Use flake inputs
Bare URLs → Always quote (RFC 45)

Phase 2: Dead Code & Redundancy

Unused let bindings and function arguments
Commented-out code blocks
Duplicate package declarations across files
if x == true → if x, if x then true else false → x

Phase 3: Consistency

camelCase for variables, kebab-case for derivations
Consistent lib usage
Consistent module structure

Phase 4: Module Structure

Large files that should be split
No circular imports
Clear dependency direction

Phase 5: Validate

nix flake check --extra-experimental-features 'nix-command flakes pipe-operators'
nix eval .#nixosConfigurations.XPS9350.config.system.build.toplevel --extra-experimental-features 'nix-command flakes pipe-operators'

Report: files modified, issues found/fixed, validation results.

Plus depuis ce dépôt

même dépôt

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	cleanup
description	Performs comprehensive cleanup of the Nix codebase. Detects anti-patterns, removes dead code, fixes inconsistencies, and validates.
when_to_use	When the user asks to clean up, lint, or improve the quality of their Nix configuration files.
allowed-tools	Read, Edit, Write, Glob, Grep, Bash(nix flake check:), Bash(nix eval:)

Nix Codebase Cleanup

Phase 1: Anti-Pattern Detection

Scan for and fix:

rec { } → Use let ... in instead (infinite recursion risk)
Top-level with → Use inherit or qualified names
Lookup paths <...> → Use flake inputs
Bare URLs → Always quote (RFC 45)

Phase 2: Dead Code & Redundancy

Unused let bindings and function arguments
Commented-out code blocks
Duplicate package declarations across files
if x == true → if x, if x then true else false → x

Phase 3: Consistency

camelCase for variables, kebab-case for derivations
Consistent lib usage
Consistent module structure

Phase 4: Module Structure

Large files that should be split
No circular imports
Clear dependency direction

Phase 5: Validate

nix flake check --extra-experimental-features 'nix-command flakes pipe-operators'
nix eval .#nixosConfigurations.XPS9350.config.system.build.toplevel --extra-experimental-features 'nix-command flakes pipe-operators'

Report: files modified, issues found/fixed, validation results.