ai-slash-commands 2026.1.4 → 2026.1.5

package/.vscode/launch.json

@@ -0,0 +1,42 @@
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "npm: gen",
+      "type": "node",
+      "request": "launch",
+      "runtimeExecutable": "npm",
+      "runtimeArgs": ["run", "gen"],
+      "console": "integratedTerminal",
+      "internalConsoleOptions": "neverOpen"
+    },
+    {
+      "name": "npm: install",
+      "type": "node",
+      "request": "launch",
+      "runtimeExecutable": "npm",
+      "runtimeArgs": ["run", "install"],
+      "console": "integratedTerminal",
+      "internalConsoleOptions": "neverOpen"
+    },
+    {
+      "name": "npm: uninstall",
+      "type": "node",
+      "request": "launch",
+      "runtimeExecutable": "npm",
+      "runtimeArgs": ["run", "uninstall"],
+      "console": "integratedTerminal",
+      "internalConsoleOptions": "neverOpen"
+    },
+    {
+      "name": "npm: link:windsurf",
+      "type": "node",
+      "request": "launch",
+      "runtimeExecutable": "npm",
+      "runtimeArgs": ["run", "link:windsurf"],
+      "console": "integratedTerminal",
+      "internalConsoleOptions": "neverOpen"
+    }
+  ]
+}
+

package/README.md

@@ -1,5 +1,14 @@
 # ai-slash-commands
 
+A tool for managing AI slash commands and prompts across multiple AI-powered editors. Write prompts once in markdown, and install them to Claude Code, Cursor, Windsurf, and Codex.
+
+**Quick start:**
+```bash
+npx ai-slash-commands
+```
+
+[Prompts list](prompts/)
+
 Один набор markdown-промптов в `./prompts/*.md`, генерация в `./dist/**` и установка в домашние папки для:
 - Claude Code
 - Cursor

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-slash-commands",
-  "version": "2026.1.4",
+  "version": "2026.1.5",
   "type": "module",
   "bin": {
     "ai-slash-commands": "scripts/cli.mjs"

package/prompts/README.md

@@ -0,0 +1,36 @@
+# Commands
+
+This directory contains AI slash command prompts.
+
+## Available Commands
+
+### `/audit-packages`
+
+# audit-packages - update packages
+
+*Source: [audit-packages.md](audit-packages.md)*
+
+### `/commit`
+
+# commit - make a commit
+
+*Source: [commit.md](commit.md)*
+
+### `/feat`
+
+# feat - add a new feature
+
+*Source: [feat.md](feat.md)*
+
+### `/learn`
+
+# learn - add agents knowledge
+
+*Source: [learn.md](learn.md)*
+
+### `/refactoring`
+
+Review the codebase, find files with many lines or a lot of duplicate code, suggest 2-3 refactoring tasks to improve the code.
+
+*Source: [refactoring.md](refactoring.md)*
+

package/prompts/audit-packages.md

@@ -0,0 +1,11 @@
+# audit-packages - update packages
+
+Check package versions for known vulnerabilities. Update vulnerable packages.
+
+Verify the application works.
+
+If it's quick, update all packages to the latest versions. If updating all packages isn't feasible, update only vulnerable ones.
+
+When changing major versions, check for breaking changes and review code that uses them.
+
+for package.json: run `npm audit fix --force`, verify the application works. First update dependencies, then devDependencies. If all packages couldn't be updated, update only vulnerable ones. When changing major versions, check for breaking changes and review code that uses them.

package/prompts/commit.md

@@ -1,6 +1,18 @@
-Собери один аккуратный коммит по текущим изменениям.
+# commit - make a commit
 
-Требования:
-- Один коммит, не несколько.
-- Сообщение коммита короткое, но информативное. Angular commit message style: feat(component), fix, test, docs, refactor, style, chore.
-- Если есть тесты - запусти их.
+Act as a senior software engineer to commit changes to the repository in this format:
+"$type${[(scope)]}{[!]}: $description"
+# Notes:
+# - Square brackets [] indicate optional parts.
+# - "!" marks a breaking change.
+
+Types: fix | feat | chore | docs | refactor | test | perf | build | ci | style | revert | other
+
+Constraints {
+  When committing, don't log about logging in the commit message.
+  Use multiple -m flags, one for each log entry.
+  Limit the first commit message line to 50 characters.
+  Use conventional commits with a scope, title, and body.
+}
+
+If there are tests in project, run them before committing.

package/prompts/feat.md

@@ -0,0 +1,68 @@
+# feat - add a new feature
+
+Act as a senior software engineer to add a new feature to the repository.
+
+### 0) Inputs and constraints
+
+* Feature request (user description)
+* Repo context (structure, stack, conventions, CI)
+* Constraints (deadline, “no refactors”, compatibility, platforms, versions)
+
+If critical info is missing, ask only the minimum set of questions required to proceed. Otherwise, make reasonable assumptions and clearly list them.
+
+### 1) Define the feature
+
+Produce:
+
+* A 1-2 sentence goal statement
+* Primary user flows (happy path + 2-3 important edge cases)
+* Definition of Done (clear acceptance criteria)
+* Constraints and compatibility notes (APIs, data, platforms, versions)
+
+### 2) Codebase reconnaissance
+
+Before editing:
+
+* Identify where this feature should live (files/modules)
+* List integration points (API/UI/CLI/config/DB)
+* Call out risks (breaking changes, migrations, flags, performance, security)
+
+### 3) Implementation plan
+
+Create a small-step plan:
+
+* What changes by file/module
+* New entities/interfaces/types/endpoints/tables (if any)
+* Minimal incremental approach: skeleton first, then expand
+* Rollback strategy and/or feature flag if risk is non-trivial
+
+### 4) Implement
+
+Make changes carefully:
+
+* Follow existing architecture and style
+* Avoid duplication; extract shared logic
+* Use clear names; add comments only when they add real value
+* Preserve backward compatibility unless explicitly instructed otherwise
+* Keep diffs focused; avoid unrelated refactors
+
+### 5) Tests
+
+* Add/update tests (unit/integration) for key flows, if tests are present in the project.
+* Include regression coverage for the behavior this feature is meant to address (when applicable)
+* If tests are difficult, explain why and provide an alternative verification plan (smoke/e2e/manual checklist)
+
+### 6) Documentation and developer experience
+
+* Update README/docs/examples as needed
+* Document new config/env variables and defaults
+* Add “How to verify locally”: commands and a couple of usage examples
+
+### 7) Final summary
+
+End with:
+
+* What changed (brief)
+* Files touched (grouped by purpose)
+* Commands to verify (lint/test/build/run)
+* Known limitations / follow-ups (if any)

package/prompts/learn.md

@@ -0,0 +1,3 @@
+# learn - add agents knowledge
+
+Look at the dialog. Add strategic knowledge to AGENTS.md, CLAUDE.md, .cursor/rules

package/prompts/refactoring.md

@@ -0,0 +1,3 @@
+# refactoring - refactor the code
+
+Review the codebase, find files with many lines or a lot of duplicate code, suggest 2-3 refactoring tasks to improve the code.

package/scripts/gen.mjs

@@ -38,6 +38,41 @@ async function listPromptFiles(promptsDir) {
     .map(e => e.name);
 }
 
+async function generateCommandsReadme(promptsDir) {
+  const promptFiles = await listPromptFiles(promptsDir);
+  const commands = [];
+
+  for (const name of promptFiles) {
+    if (name.toLowerCase() === "readme.md") {
+      continue; // Skip README.md itself
+    }
+    const srcPath = path.join(promptsDir, name);
+    const content = await fs.readFile(srcPath, "utf8");
+    const commandName = name.replace(/\.md$/i, "");
+    const firstLine = content.split("\n")[0].trim();
+    const description = firstLine || "No description";
+    commands.push({ name: commandName, description, filename: name });
+  }
+
+  // Sort commands alphabetically by name
+  commands.sort((a, b) => a.name.localeCompare(b.name));
+
+  // Generate README content
+  let readmeContent = "# Commands\n\n";
+  readmeContent += "This directory contains AI slash command prompts.\n\n";
+  readmeContent += "## Available Commands\n\n";
+
+  for (const cmd of commands) {
+    readmeContent += `### \`/${cmd.name}\`\n\n`;
+    readmeContent += `${cmd.description}\n\n`;
+    readmeContent += `*Source: [${cmd.filename}](${cmd.filename})*\n\n`;
+  }
+
+  const readmePath = path.join(promptsDir, "README.md");
+  await fs.writeFile(readmePath, readmeContent, "utf8");
+  console.log(`Generated: ${path.relative(repoRoot, readmePath)}`);
+}
+
 export async function generate({ targets, promptsDir }) {
   const promptFiles = await listPromptFiles(promptsDir);
   if (promptFiles.length === 0) {
@@ -54,6 +89,9 @@ export async function generate({ targets, promptsDir }) {
   }
 
   for (const name of promptFiles) {
+    if (name.toLowerCase() === "readme.md") {
+      continue; // Skip README.md
+    }
     const srcPath = path.join(promptsDir, name);
     const content = await fs.readFile(srcPath, "utf8");
 
@@ -63,6 +101,9 @@ export async function generate({ targets, promptsDir }) {
     }
   }
 
+  // Generate commands README in prompts directory
+  await generateCommandsReadme(promptsDir);
+
   console.log("Generated:");
   for (const t of targets) {
     console.log(`- dist/${TARGETS[t].out}/`);

package/scripts/install.mjs

@@ -65,7 +65,9 @@ function parseArgs() {
   return { targets };
 }
 
-export async function install({ targets }) {
+async function main() {
+  const { targets } = parseArgs();
+
   for (const t of targets) {
     if (!SRC[t] || !DEST[t]) {
       console.error(`Unknown target: ${t}. Allowed: ${Object.keys(SRC).join(", ")}`);
@@ -79,15 +81,7 @@ export async function install({ targets }) {
   }
 }
 
-async function main() {
-  const { targets } = parseArgs();
-  await install({ targets });
-}
-
-const isMain = process.argv[1] && fileURLToPath(import.meta.url) === path.resolve(process.argv[1]);
-if (isMain) {
-  main().catch((err) => {
-    console.error(err);
-    process.exit(1);
-  });
-}
+main().catch((err) => {
+  console.error(err);
+  process.exit(1);
+});