ai-slash-commands 2026.1.6 → 2026.1.7

package/.vscode/launch.json

@@ -40,3 +40,5 @@
   ]
 }
 
+
+

package/.vscode/settings.json

@@ -0,0 +1,9 @@
+{
+  "terminal.integrated.profiles.windows": {
+    "pc-virt ai-slash-commands": {
+      "path": "C:\\Windows\\System32\\OpenSSH\\ssh.exe",
+      "args": ["-t", "pc-virt-ai-slash-commands"]
+    }
+  },
+  "terminal.integrated.defaultProfile.windows": "pc-virt ai-slash-commands"
+}

package/README.md

@@ -9,6 +9,9 @@ npx ai-slash-commands
 
 [Prompts list](prompts/)
 
+Some of commands was copied from:
+- https://github.com/hamzafer/cursor-commands
+
 Один набор markdown-промптов в `./prompts/*.md`, генерация в `./dist/**` и установка в домашние папки для:
 - Claude Code
 - Cursor

package/package.json

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

package/prompts/clarify-task.md

@@ -0,0 +1,17 @@
+# Clarify Task
+
+Before doing ANY coding work on the task I describe:
+
+1. **Ask clarifying questions** - Use 2-4 multiple choice questions to clarify requirements:
+
+    - Data flow and architecture
+    - APIs and integrations
+    - Authentication/authorization
+    - Edge cases and error handling
+    - UI/UX expectations (if applicable)
+
+2. **Restate requirements** - After I answer, restate the final requirements in your own words to confirm understanding.
+
+3. **Confirm before proceeding** - ONLY then ask if I want to proceed to planning/implementation.
+
+Keep asking questions until you have enough context to give an accurate & confident answer.

package/prompts/deslop.md

@@ -0,0 +1,12 @@
+# Remove AI code slop
+
+Check the diff against main, and remove all AI generated slop introduced in this branch.
+
+This includes:
+
+- Extra comments that a human wouldn't add or is inconsistent with the rest of the file
+- Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted / validated codepaths)
+- Casts to any to get around type issues
+- Any other style that is inconsistent with the file
+
+Report at the end with only a 1-3 sentence summary of what you changed

package/prompts/docs.md

@@ -0,0 +1,40 @@
+# Add Documentation
+
+## Overview
+
+Add comprehensive documentation for the current code/feature and format it according to the project's documentation standards, including it in the appropriate location (README, docs folder, or inline comments).
+
+## Steps
+
+1. **Overview**
+    - What this code/feature does
+    - Why it exists and its purpose
+    - Key concepts and terminology
+2. **API Documentation**
+    - Function/method signatures
+    - Parameters and return values
+    - Example usage with code snippets
+    - Error handling and edge cases
+3. **Implementation Details**
+    - Architecture overview
+    - Important design decisions
+    - Dependencies and integrations
+4. **Examples**
+    - Common use cases with full examples
+    - Best practices and patterns
+    - Common pitfalls to avoid
+
+## Add Documentation Checklist
+
+- [ ] Explained what this code/feature does
+- [ ] Documented why it exists and its purpose
+- [ ] Defined key concepts and terminology
+- [ ] Documented function/method signatures
+- [ ] Documented parameters and return values
+- [ ] Included example usage with code snippets
+- [ ] Documented error handling and edge cases
+- [ ] Provided architecture overview
+- [ ] Documented important design decisions
+- [ ] Included common use cases with full examples
+- [ ] Documented best practices and patterns
+- [ ] Documented common pitfalls to avoid

package/prompts/push.md

@@ -0,0 +1,20 @@
+# Git Push (sync with origin)
+
+## Overview
+
+Push current branch to origin and sync with remote updates.
+
+## Steps
+
+1. **Fetch and rebase onto latest main (optional but recommended)**
+    - `git fetch origin`
+    - `git rebase origin/main || git rebase --abort` (if not on main, rebase your feature branch onto latest main)
+2. **Push current branch**
+    - `git push -u origin HEAD`
+3. **If push rejected due to remote updates**
+    - Rebase and push: `git pull --rebase && git push`
+
+## Notes
+
+- Prefer `rebase` over `merge` for a linear history.
+- If you need to force push after a rebase: you need to ask the user if they want to force push: `git push --force-with-lease`.

package/prompts/refactor-code.md

@@ -0,0 +1,35 @@
+# Refactor Code
+
+## Overview
+
+Refactor the selected code to improve its quality while maintaining the same functionality, providing the refactored code with explanations of the improvements made.
+
+## Steps
+
+1. **Code Quality Improvements**
+    - Extract reusable functions or components
+    - Eliminate code duplication
+    - Improve variable and function naming
+    - Simplify complex logic and reduce nesting
+2. **Performance Optimizations**
+    - Identify and fix performance bottlenecks
+    - Optimize algorithms and data structures
+    - Reduce unnecessary computations
+    - Improve memory usage
+3. **Maintainability**
+    - Make the code more readable and self-documenting
+    - Add appropriate comments where needed
+    - Follow SOLID principles and design patterns
+    - Improve error handling and edge case coverage
+
+## Refactor Code Checklist
+
+- [ ] Extracted reusable functions or components
+- [ ] Eliminated code duplication
+- [ ] Improved variable and function naming
+- [ ] Simplified complex logic and reduced nesting
+- [ ] Identified and fixed performance bottlenecks
+- [ ] Optimized algorithms and data structures
+- [ ] Made code more readable and self-documenting
+- [ ] Followed SOLID principles and design patterns
+- [ ] Improved error handling and edge case coverage

package/prompts/security-audit.md

@@ -0,0 +1,29 @@
+# Security Audit
+
+## Overview
+
+Comprehensive security review to identify and fix vulnerabilities in the
+codebase.
+
+## Steps
+
+1. **Dependency audit**
+    - Check for known vulnerabilities
+    - Update outdated packages
+    - Review third-party dependencies
+2. **Code security review**
+    - Check for common vulnerabilities
+    - Review authentication/authorization
+    - Audit data handling practices
+3. **Infrastructure security**
+    - Review environment variables
+    - Check access controls
+    - Audit network security
+
+## Security Checklist
+
+- [ ] Dependencies updated and secure
+- [ ] No hardcoded secrets
+- [ ] Input validation implemented
+- [ ] Authentication secure
+- [ ] Authorization properly configured