From d119e2322f6bcb4dc434d003c8c3290326b39f94 Mon Sep 17 00:00:00 2001 From: Amolith Date: Sat, 8 Nov 2025 10:19:52 -0700 Subject: [PATCH] feat(crush): add np commands --- dot_config/crush/commands/np-r.md | 1 + dot_config/crush/commands/np-s.md | 7 +++++++ dot_config/crush/commands/{simple.md => np-s_ref.md} | 0 3 files changed, 8 insertions(+) create mode 100644 dot_config/crush/commands/np-r.md create mode 100644 dot_config/crush/commands/np-s.md rename dot_config/crush/commands/{simple.md => np-s_ref.md} (100%) diff --git a/dot_config/crush/commands/np-r.md b/dot_config/crush/commands/np-r.md new file mode 100644 index 0000000000000000000000000000000000000000..39db663afe62bdcc1a838f8916bbca02d449e9e5 --- /dev/null +++ b/dot_config/crush/commands/np-r.md @@ -0,0 +1 @@ +Hey there! Our session got interrupted—please resume it with `np r` and follow the instructions in `np`'s output. Thank you. diff --git a/dot_config/crush/commands/np-s.md b/dot_config/crush/commands/np-s.md new file mode 100644 index 0000000000000000000000000000000000000000..de537d8243dd392d244d4a68229ac342961f8a86 --- /dev/null +++ b/dot_config/crush/commands/np-s.md @@ -0,0 +1,7 @@ +Hey there :) We're having the following issue. + + +$DESCRIPTION + + +Please consider it, and if you already know which files are relevant, go ahead and read them. If you don't, list the contents of some directories and read just the files that seem relevant. Your goal during reading is getting a better idea of what changes might be necessary to resolve the issue. After you're done reading and you have a solid understanding, start your `np` session with `np s`. After setting up the goal and making sure its description refers to to the related files, think deeply, then add your tasks and get started on them. diff --git a/dot_config/crush/commands/simple.md b/dot_config/crush/commands/np-s_ref.md similarity index 100% rename from dot_config/crush/commands/simple.md rename to dot_config/crush/commands/np-s_ref.md