lite-kits 0.1.0__py3-none-any.whl → 0.1.1__py3-none-any.whl

lite_kits/kits/dev/github/prompts/review.prompt.md

@@ -0,0 +1,202 @@
+---
+description: Review staged changes against best practices
+---
+
+# Code Review of Staged Changes
+
+**Purpose**: Review staged git changes for quality, best practices, and potential issues before committing.
+
+## Execution Steps
+
+Execute the following steps to review staged changes:
+
+### 1. Check Staged Files
+
+```bash
+# Get list of staged files with status
+git diff --staged --name-status
+```
+
+**If no files are staged**:
+- Inform user that nothing is staged
+- Suggest running `git add` or `@terminal /commit` to stage and commit together
+- Exit gracefully
+
+### 2. Analyze Staged Changes
+
+```bash
+# Get the actual diff with context
+git diff --staged
+```
+
+### 3. Review Changes
+
+Analyze the diff output for:
+
+**✅ Good Practices to Acknowledge**:
+- Clear, descriptive function/variable names
+- Appropriate comments where needed
+- Consistent formatting
+- Type hints (Python) or type annotations
+- Test coverage for new code
+- Error handling
+- Input validation
+
+**⚠️ Issues to Flag**:
+- **Security**:
+  - Hardcoded credentials or API keys
+  - SQL injection vulnerabilities
+  - XSS vulnerabilities
+  - Unsafe deserialization
+  - Missing authentication/authorization checks
+  
+- **Code Quality**:
+  - TODOs or FIXMEs (should be tracked in issues)
+  - Commented-out code blocks
+  - Magic numbers without explanation
+  - Overly complex functions (>50 lines)
+  - Duplicate code patterns
+  - Inconsistent naming conventions
+  
+- **Best Practices**:
+  - Missing error handling
+  - No logging for important operations
+  - Hardcoded configuration values
+  - Missing input validation
+  - Unused imports or variables
+  - Missing docstrings for public APIs
+
+### 4. Present Review Results
+
+Format output as follows:
+
+```
+## Code Review Results
+
+**Staged files**: [count]
+[list files with status: A=added, M=modified, D=deleted]
+
+**Summary of changes**:
+[brief description of what's being changed]
+
+===========================================================
+**✅ Good Practices Found:**
+===========================================================
+
+[List positive findings, grouped by file]
+- [file]: [specific good practice observed]
+
+===========================================================
+**⚠️ Suggestions for Improvement:**
+===========================================================
+
+[List issues/suggestions, grouped by file with line numbers if possible]
+- [file]:[line]: [specific issue and suggested fix]
+
+===========================================================
+**🔒 Security Check:**
+===========================================================
+
+[Report any security concerns or confirm none found]
+- ✓ No hardcoded credentials detected
+- ✓ No obvious security vulnerabilities
+- ⚠ [Any security concerns]
+
+===========================================================
+**📊 Overall Assessment:**
+===========================================================
+
+[One of: "Ready to commit", "Ready with minor suggestions", "Needs changes"]
+
+[Brief summary of overall code quality]
+
+**Recommendation**: [Approve / Address suggestions / Do not commit]
+```
+
+### 5. Handle User Response
+
+After presenting results, wait for user action. They may:
+- Proceed with commit anyway
+- Make changes and re-review
+- Cancel the review
+
+## Example Output
+
+```
+## Code Review Results
+
+**Staged files**: 3
+- A  src/auth.py (new file)
+- M  src/models.py (modified)
+- A  tests/test_auth.py (new file)
+
+**Summary of changes**:
+Adding user authentication system with bcrypt password hashing
+and JWT token generation.
+
+===========================================================
+**✅ Good Practices Found:**
+===========================================================
+
+- src/auth.py: Clear function names (hash_password, verify_password)
+- src/auth.py: Type hints used throughout
+- src/auth.py: Comprehensive docstrings for all functions
+- src/models.py: Proper SQLAlchemy relationship definitions
+- tests/test_auth.py: Good test coverage with fixtures
+
+===========================================================
+**⚠️ Suggestions for Improvement:**
+===========================================================
+
+- src/auth.py:45: Consider extracting hash_password to utils module
+  Current: Function in auth.py
+  Suggest: Move to src/utils/crypto.py for reusability
+
+- src/models.py:12: TODO comment present
+  Line: "# TODO: Add password reset functionality"
+  Suggest: Create GitHub issue and reference it in comment
+
+- tests/test_auth.py:67: Missing edge case test
+  Suggest: Add test for empty password input
+
+- src/auth.py:23: Magic number for token expiration
+  Current: expires_delta = timedelta(hours=24)
+  Suggest: Move to config file or environment variable
+
+===========================================================
+**🔒 Security Check:**
+===========================================================
+
+✓ No hardcoded credentials detected
+✓ Using bcrypt for password hashing (good choice!)
+✓ JWT tokens generated securely
+⚠ Consider adding rate limiting to prevent brute force attacks
+
+===========================================================
+**📊 Overall Assessment:**
+===========================================================
+
+**Status**: Ready with minor suggestions
+
+The code follows good practices with proper type hints, docstrings,
+and test coverage. The suggestions above are minor improvements that
+can be addressed now or in future iterations.
+
+**Recommendation**: Approve and commit - suggestions are non-blocking
+```
+
+## Important Notes
+
+- This command is **read-only** - it never modifies files
+- Focus on **actionable feedback** - be specific about what to change
+- Be **encouraging** - acknowledge good practices
+- **Security first** - always check for security issues
+- Keep review **concise** - don't overwhelm with minor issues
+- **Respect the agent's work** - balance critique with acknowledgment
+
+## Integration with Other Commands
+
+- Run `@terminal /review` before `@terminal /commit` to catch issues early
+- Use after making changes and staging them with `git add`
+- Combine with `@terminal /pr` workflow - review before creating PR
+- Works great in multi-agent workflows (one agent reviews another's work)

lite_kits/kits/dev/github/prompts/stats.prompt.md

@@ -0,0 +1,163 @@
+---
+description: Generate concise project metrics for AI agent orientation
+---
+
+# Project Statistics
+
+**Purpose**: Provide quick project overview metrics for AI agents joining a project or assessing scope.
+
+## Execution Steps
+
+Execute the following steps to gather project statistics:
+
+### 1. Count Lines of Code
+
+**Preferred method** (if tokei installed):
+```powershell
+# Check if tokei is available
+Get-Command tokei -ErrorAction SilentlyContinue
+
+# If available, use tokei for fast, accurate counts
+tokei --output json
+```
+
+**Fallback method** (if tokei not available):
+```powershell
+# Python
+(Get-ChildItem -Recurse -Filter *.py | Get-Content | Measure-Object -Line).Lines
+
+# JavaScript/TypeScript
+(Get-ChildItem -Recurse -Include *.js,*.ts | Get-Content | Measure-Object -Line).Lines
+
+# Markdown
+(Get-ChildItem -Recurse -Filter *.md | Get-Content | Measure-Object -Line).Lines
+
+# All files combined
+(Get-ChildItem -Recurse -File | Get-Content | Measure-Object -Line).Lines
+```
+
+### 2. Count Files and Directories
+
+```powershell
+# Count files (excluding hidden)
+(Get-ChildItem -Recurse -File | Where-Object { -not $_.FullName.Contains('\.') }).Count
+
+# Count directories (excluding hidden)
+(Get-ChildItem -Recurse -Directory | Where-Object { -not $_.FullName.Contains('\.') }).Count
+```
+
+### 3. Get Git History Summary
+
+```powershell
+# Total commits
+(git log --oneline | Measure-Object).Count
+
+# Contributor count
+(git log --format='%aN' | Sort-Object -Unique).Count
+
+# Recent activity
+git log --oneline -5
+```
+
+If not a git repository, skip this section.
+
+### 4. Check for Test Coverage
+
+Look for common coverage report files:
+```powershell
+# Python coverage files
+Get-ChildItem -Path . -Include .coverage,coverage.xml -Recurse -ErrorAction SilentlyContinue
+Get-ChildItem -Path htmlcov -Directory -ErrorAction SilentlyContinue
+
+# JavaScript coverage
+Get-ChildItem -Path coverage,.nyc_output -Directory -ErrorAction SilentlyContinue
+
+# If coverage files exist, try to extract percentage
+# Python: coverage report | Select-String TOTAL
+# JavaScript: Get-Content coverage/coverage-summary.json | ConvertFrom-Json
+```
+
+### 5. Generate Concise Table Output
+
+Provide stats in this format (~20 lines max):
+
+```markdown
+## Project Statistics
+
+**Code**:
+- Language1: X,XXX LOC (NN%)
+- Language2: XXX LOC (NN%)
+- Language3: XX LOC (NN%)
+
+**Structure**:
+- NN files, NN directories
+- NNN commits, N contributors
+
+**Testing**:
+- Coverage: NN% (or N/A)
+- Tests: NN files (or N/A)
+
+**Next Action**: [Explore src/ / Review tests / Check docs]
+```
+
+## Important Notes
+
+- **Be concise**: Keep output under 20 lines
+- **Use tables**: Well-formatted markdown tables or lists
+- **Handle missing tools**:
+  - No tokei → Use Get-ChildItem/Measure-Object fallback, note "Basic LOC count"
+  - Not a git repo → Skip git section, note "No git history"
+  - No coverage → Show "N/A" gracefully
+
+- **Percentages**: Calculate language percentages from total LOC
+- **Large repos**: If >100k LOC, note "Large project" and consider sampling
+- **Speed**: Target <5 second execution time
+
+## Edge Cases
+
+- **No git repository**: Skip git section, show file/LOC stats only
+- **No test coverage reports**: Show "Coverage: N/A"
+- **Tokei not installed**: Use PowerShell fallback, note in output
+- **Very large repo (1M+ LOC)**: Sample or provide high-level summary only
+- **No code files**: "Appears to be a documentation-only or data project"
+
+## Example Output
+
+```markdown
+## Project Statistics
+
+**Code**:
+- Python: 2,453 LOC (87%)
+- Markdown: 342 LOC (12%)
+- YAML: 28 LOC (1%)
+- Total: 2,823 LOC
+
+**Structure**:
+- 45 files, 12 directories
+- 127 commits, 3 contributors
+
+**Testing**:
+- Coverage: 78% (via pytest-cov)
+- Tests: 23 test files
+
+**Next Action**: Explore src/ directory to understand core modules
+```
+
+```markdown
+## Project Statistics
+
+**Code** (tokei not available, using basic count):
+- Python: ~1,200 lines
+- Markdown: ~400 lines
+- Total: ~1,600 lines (approximate)
+
+**Structure**:
+- 32 files, 8 directories
+- Not a git repository
+
+**Testing**:
+- Coverage: N/A
+- Tests: N/A
+
+**Next Action**: Check if this is a standalone library or tool
+```

lite_kits/kits/git/README.md

@@ -2,7 +2,7 @@
 
 **Status**: ✅ Recommended (Default)
 
-Git workflow automation with smart commits, PR creation, sync visualization, and cleanup operations. Includes ASCII visualization for better readability.
+Git workflow automation with smart commits, PR creation, code review, and cleanup operations. Includes ASCII visualization for better readability.
 
 ## What It Adds
 
@@ -12,7 +12,7 @@ Git workflow automation with smart commits, PR creation, sync visualization, and
 |---------|-------------|----------------|-------------|
 | `/commit` | 🚧 | 🚧 | Smart commit with agent attribution |
 | `/pr` | 🚧 | 🚧 | Create PR with auto-generated description |
-| `/sync` | 🚧 | 🚧 | Show sync status with ASCII visualization |
+| `/review` | 🚧 | 🚧 | Review staged changes against best practices |
 | `/cleanup` | 🚧 | 🚧 | Clean merged branches, stale worktrees |
 
 🚧 = Coming Soon
@@ -36,12 +36,12 @@ your-project/
 ├── .claude/commands/          # If Claude Code detected
 │   ├── commit.md
 │   ├── pr.md
-│   ├── sync.md
+│   ├── review.md
 │   └── cleanup.md
 └── .github/prompts/           # If GitHub Copilot detected
     ├── commit.prompt.md
     ├── pr.prompt.md
-    ├── sync.prompt.md
+    ├── review.prompt.md
     └── cleanup.prompt.md
 ```
 
@@ -102,6 +102,55 @@ via claude-sonnet-4.5 @ claude-code
 
 ---
 
+### `/review` - Code Review (Coming Soon)
+
+**Purpose**: Review staged changes against best practices and project standards.
+
+**What it will do**:
+1. Run `git diff --staged` to see changes
+2. Check changes against common best practices
+3. Identify potential code smells
+4. Suggest improvements
+5. Verify consistent formatting
+6. Check for common issues (hardcoded secrets, TODO comments, etc.)
+
+**Example usage** (planned):
+```
+/review
+
+## Code Review
+
+**Staged files**: 3
+- src/auth.py (new)
+- src/models.py (modified)
+- tests/test_auth.py (new)
+
+**Analysis**:
+
+✅ **Good practices**:
+- Clear function names and docstrings
+- Comprehensive test coverage (94%)
+- Type hints used throughout
+- No hardcoded credentials
+
+⚠ **Suggestions**:
+- src/auth.py:45: Consider extracting hash_password to utils
+- src/models.py:12: TODO comment should be tracked in issue
+- tests/test_auth.py: Add edge case for empty passwords
+
+**Overall**: Ready to commit with minor suggestions
+
+**Approve?** (y/n): y
+```
+
+**Benefits**:
+- Catch issues before committing
+- Consistent code quality
+- Learn best practices
+- Agent-to-agent code review support
+
+---
+
 ### `/pr` - Create Pull Request (Coming Soon)
 
 **Purpose**: Create PR with auto-generated description from commits.
@@ -166,64 +215,6 @@ via claude-sonnet-4.5 @ claude-code
 
 ---
 
-### `/sync` - Sync Status with Visualization (Coming Soon)
-
-**Purpose**: Show git sync status with ASCII visualization.
-
-**Problem**: `git status` output is text-heavy and hard to parse visually.
-
-**Solution**: ASCII tree diagrams and colorized status.
-
-**Example usage** (planned):
-```
-/sync
-
-## Git Sync Status
-
-**Branch**: dev/003-auth
-**Tracking**: origin/dev/003-auth
-
-**Local vs Remote**:
-
-    origin/main ─────────────┬──────> main (up to date)
-                              │
-                              ├──────> dev/003-auth (5 commits ahead)
-                              │        ↑ PUSH NEEDED
-                              │
-    Your commits:             │
-    ├─ a1b2c3d feat: Add auth│
-    ├─ b2c3d4e feat: Add user│
-    ├─ c3d4e5f test: Add auth│
-    ├─ d4e5f6g docs: Update  │
-    └─ e5f6g7h fix: Resolve  │
-                              │
-**Status**:
-✓ No uncommitted changes
-⚠ 5 commits not pushed
-✓ Up to date with remote (fetched 2m ago)
-
-**Actions**:
-1. git push origin dev/003-auth
-2. git fetch (refresh remote status)
-3. /pr (create pull request)
-
-**Worktrees** (if any):
-None active
-
-**Branches** (recent):
-- dev/003-auth (current) ← 5 commits ahead
-- main (up to date)
-- dev/002-blog (merged, can cleanup)
-```
-
-**Benefits**:
-- Visual understanding at a glance
-- Clear action items
-- Worktree awareness
-- Branch cleanup suggestions
-
----
-
 ### `/cleanup` - Git Cleanup (Coming Soon)
 
 **Purpose**: Clean up merged branches, stale worktrees, and old features.
@@ -317,17 +308,17 @@ Commits ahead of main:
 ## Use Cases
 
 ### Daily Development
-**Use**: `/commit` for every commit, `/sync` multiple times per day
+**Use**: `/review` before committing, `/commit` for every commit
 
 ### Before Creating PR
-**Use**: `/sync` to ensure up to date, `/pr` to create pull request
+**Use**: `/review` final check, `/pr` to create pull request
 
 ### Weekly Maintenance
 **Use**: `/cleanup` to remove merged branches and free up space
 
 ### Multi-Agent Projects
-**Combine with**: multiagent-kit for coordination
-**Use**: `/sync` shows worktree status for parallel development
+**Combine with**: multiagent-kit for coordination and `/sync` command
+**Use**: `/review` for agent-to-agent code review
 
 ---
 
@@ -357,8 +348,8 @@ lite-kits remove -Kit git
 ```
 
 Removes:
-- `.claude/commands/{commit,pr,sync,cleanup}.md`
-- `.github/prompts/{commit,pr,sync,cleanup}.prompt.md`
+- `.claude/commands/{commit,pr,review,cleanup}.md`
+- `.github/prompts/{commit,pr,review,cleanup}.prompt.md`
 
 ---