From bf72239794d957a67afcbe62adcfc23882d03dbd Mon Sep 17 00:00:00 2001 From: alexion Date: Thu, 17 Sep 2026 01:35:46 -0400 Subject: [PATCH] refactor(prompts): remove language-specific style review --- .pi/prompts/review-nix.md | 31 ------------------------------- 1 file changed, 31 deletions(-) delete mode 100644 .pi/prompts/review-nix.md diff --git a/.pi/prompts/review-nix.md b/.pi/prompts/review-nix.md deleted file mode 100644 index 7339187..0000000 --- a/.pi/prompts/review-nix.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -description: Review Nix changes against repository Nix style rules -argument-hint: "[target]" ---- - -Use the `nix-style` skill. -Audit ${ARGUMENTS:-the staged diff} for violations of the repository Nix style rules. - -Report only actionable findings. -Order findings by severity. -Do not report preferences unless a loaded rule states them. - -Use this format for each finding: - -```text -`code-path:line` -> `smallest reviewed-code excerpt that shows the violation` - -`rule-file:line`: Finding title. -Summary: why the code breaks the rule -Fix: suggested fix -``` - -Keep the code excerpt to one to three lines when possible. -Use a longer excerpt only when the violation needs surrounding context. -Use `...` to omit unrelated lines from a multi-line excerpt. -Use a skill-relative rule citation, such as `let.md:7`. -Make the fix direct. -Do not include alternatives when one fix best follows the cited rule. - -It is acceptable to report no findings when the reviewed Nix already follows the loaded rules.