Initial commit
This commit is contained in:
27
commands/analyze-deps.md
Normal file
27
commands/analyze-deps.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
description: Analyze project dependencies for security vulnerabilities and outdated packages
|
||||
---
|
||||
|
||||
# Dependency Analysis Command
|
||||
|
||||
Analyze project dependencies for security issues and version updates.
|
||||
|
||||
## Context
|
||||
|
||||
- Current directory: !`pwd`
|
||||
- Package files: !`find . -maxdepth 2 -name "package.json" -o -name "requirements.txt" -o -name "go.mod" -o -name "Cargo.toml" 2>/dev/null`
|
||||
|
||||
## Your Task
|
||||
|
||||
1. Identify the project's dependency management system
|
||||
2. Check for:
|
||||
- Security vulnerabilities in dependencies
|
||||
- Outdated packages
|
||||
- Dependency conflicts
|
||||
3. Provide a clear summary with:
|
||||
- Total dependencies
|
||||
- Number of vulnerabilities (if any)
|
||||
- Critical updates recommended
|
||||
4. Suggest commands to update or fix issues
|
||||
|
||||
Use appropriate tools like `npm audit`, `pip-audit`, or equivalent for the detected project type.
|
||||
38
commands/project-stats.md
Normal file
38
commands/project-stats.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
description: Generate comprehensive project statistics including LOC, file counts, and language breakdown
|
||||
---
|
||||
|
||||
# Project Statistics Command
|
||||
|
||||
Generate detailed statistics about the current project.
|
||||
|
||||
## Context
|
||||
|
||||
- Current directory: !`pwd`
|
||||
- Git status: !`git status --short 2>/dev/null || echo "Not a git repository"`
|
||||
|
||||
## Your Task
|
||||
|
||||
Provide comprehensive project statistics:
|
||||
|
||||
1. **File Statistics**
|
||||
- Total number of files
|
||||
- Breakdown by file type
|
||||
- Largest files (top 5)
|
||||
|
||||
2. **Code Metrics**
|
||||
- Lines of code by language
|
||||
- Total LOC
|
||||
- Comment ratio (if detectable)
|
||||
|
||||
3. **Git Information** (if available)
|
||||
- Current branch
|
||||
- Number of commits
|
||||
- Contributors
|
||||
- Last commit date
|
||||
|
||||
4. **Project Health**
|
||||
- Presence of README, LICENSE, tests
|
||||
- Configuration files present
|
||||
|
||||
Present the information in a clean, organized format using tables or lists.
|
||||
26
commands/quick-test.md
Normal file
26
commands/quick-test.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
description: Run tests for the current project quickly
|
||||
allowed-tools: Bash(npm:*), Bash(pytest:*), Bash(go:*), Bash(cargo:*)
|
||||
---
|
||||
|
||||
# Quick Test Command
|
||||
|
||||
Run the appropriate test suite based on the project type.
|
||||
|
||||
## Context
|
||||
|
||||
- Current directory: !`pwd`
|
||||
- Package manager files: !`ls -la | grep -E "(package\.json|requirements\.txt|go\.mod|Cargo\.toml)"`
|
||||
|
||||
## Your Task
|
||||
|
||||
1. Detect the project type based on files present
|
||||
2. Run the appropriate test command:
|
||||
- Node.js: `npm test` or `npm run test`
|
||||
- Python: `pytest` or `python -m pytest`
|
||||
- Go: `go test ./...`
|
||||
- Rust: `cargo test`
|
||||
3. Display the test results clearly
|
||||
4. If tests fail, provide a brief summary of failures
|
||||
|
||||
IMPORTANT: Only use the tools specified in allowed-tools. Do not use any other tools.
|
||||
Reference in New Issue
Block a user