diff --git a/dot_config/crush/commands/np-r.md b/dot_config/crush/commands/np-r.md deleted file mode 100644 index 39db663afe62bdcc1a838f8916bbca02d449e9e5..0000000000000000000000000000000000000000 --- a/dot_config/crush/commands/np-r.md +++ /dev/null @@ -1 +0,0 @@ -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 deleted file mode 100644 index e03c9842a170e28b5296c5b09acc1238f3ff4d70..0000000000000000000000000000000000000000 --- a/dot_config/crush/commands/np-s.md +++ /dev/null @@ -1,7 +0,0 @@ -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 session with `np s` and follow the instructions in its output. diff --git a/dot_config/crush/commands/np-s_ref.md b/dot_config/crush/commands/np-s_ref.md deleted file mode 100644 index 23ce603986c32cca233cec80a8e6efa9c91ca3f8..0000000000000000000000000000000000000000 --- a/dot_config/crush/commands/np-s_ref.md +++ /dev/null @@ -1 +0,0 @@ -Hey there :) Please take a look at $REFERENCE. 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 session with `np s` and follow the instructions in its output.