lite-kits 0.1.1__py3-none-any.whl → 0.3.2__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- lite_kits/__init__.py +56 -4
- lite_kits/cli.py +782 -189
- lite_kits/core/__init__.py +6 -0
- lite_kits/core/banner.py +1 -1
- lite_kits/core/conflict_checker.py +115 -0
- lite_kits/core/detector.py +177 -0
- lite_kits/core/installer.py +242 -351
- lite_kits/core/manifest.py +146 -146
- lite_kits/core/validator.py +183 -0
- lite_kits/kits/README.md +6 -6
- lite_kits/kits/dev/README.md +241 -241
- lite_kits/kits/dev/{claude/commands → commands/.claude}/audit.md +143 -143
- lite_kits/kits/dev/{claude/commands → commands/.claude}/cleanup.md +2 -2
- lite_kits/kits/{git/claude/commands → dev/commands/.claude}/commit.md +2 -2
- lite_kits/kits/{project/claude/commands → dev/commands/.claude}/orient.md +3 -4
- lite_kits/kits/{git/claude/commands → dev/commands/.claude}/pr.md +1 -1
- lite_kits/kits/{git/claude/commands → dev/commands/.claude}/review.md +202 -202
- lite_kits/kits/{project/claude/commands → dev/commands/.claude}/stats.md +162 -162
- lite_kits/kits/{project/github/prompts → dev/commands/.github}/audit.prompt.md +143 -143
- lite_kits/kits/{git/github/prompts → dev/commands/.github}/cleanup.prompt.md +2 -2
- lite_kits/kits/{git/github/prompts → dev/commands/.github}/commit.prompt.md +2 -2
- lite_kits/kits/dev/{github/prompts → commands/.github}/orient.prompt.md +3 -4
- lite_kits/kits/{git/github/prompts → dev/commands/.github}/pr.prompt.md +1 -1
- lite_kits/kits/{git/github/prompts → dev/commands/.github}/review.prompt.md +202 -202
- lite_kits/kits/dev/{github/prompts → commands/.github}/stats.prompt.md +163 -163
- lite_kits/kits/kits.yaml +497 -180
- lite_kits/kits/multiagent/README.md +6 -6
- lite_kits/kits/multiagent/{claude/commands → commands/.claude}/sync.md +331 -331
- lite_kits/kits/multiagent/{github/prompts → commands/.github}/sync.prompt.md +73 -69
- lite_kits/kits/multiagent/memory/git-worktrees-protocol.md +370 -370
- lite_kits/kits/multiagent/memory/parallel-work-protocol.md +536 -536
- lite_kits/kits/multiagent/memory/pr-workflow-guide.md +275 -275
- lite_kits/kits/multiagent/templates/collaboration-structure/README.md +166 -166
- lite_kits/kits/multiagent/templates/decision.md +79 -79
- lite_kits/kits/multiagent/templates/handoff.md +95 -95
- lite_kits/kits/multiagent/templates/session-log.md +68 -68
- lite_kits-0.3.2.dist-info/METADATA +259 -0
- lite_kits-0.3.2.dist-info/RECORD +41 -0
- {lite_kits-0.1.1.dist-info → lite_kits-0.3.2.dist-info}/licenses/LICENSE +21 -21
- lite_kits/kits/dev/claude/commands/commit.md +0 -612
- lite_kits/kits/dev/claude/commands/orient.md +0 -146
- lite_kits/kits/dev/claude/commands/pr.md +0 -593
- lite_kits/kits/dev/claude/commands/review.md +0 -202
- lite_kits/kits/dev/claude/commands/stats.md +0 -162
- lite_kits/kits/dev/github/prompts/audit.prompt.md +0 -143
- lite_kits/kits/dev/github/prompts/cleanup.prompt.md +0 -382
- lite_kits/kits/dev/github/prompts/commit.prompt.md +0 -591
- lite_kits/kits/dev/github/prompts/pr.prompt.md +0 -603
- lite_kits/kits/dev/github/prompts/review.prompt.md +0 -202
- lite_kits/kits/git/README.md +0 -365
- lite_kits/kits/git/claude/commands/cleanup.md +0 -361
- lite_kits/kits/git/scripts/bash/get-git-context.sh +0 -208
- lite_kits/kits/git/scripts/powershell/Get-GitContext.ps1 +0 -242
- lite_kits/kits/project/README.md +0 -228
- lite_kits/kits/project/claude/commands/audit.md +0 -143
- lite_kits/kits/project/claude/commands/review.md +0 -112
- lite_kits/kits/project/github/prompts/orient.prompt.md +0 -150
- lite_kits/kits/project/github/prompts/review.prompt.md +0 -112
- lite_kits/kits/project/github/prompts/stats.prompt.md +0 -163
- lite_kits-0.1.1.dist-info/METADATA +0 -447
- lite_kits-0.1.1.dist-info/RECORD +0 -58
- {lite_kits-0.1.1.dist-info → lite_kits-0.3.2.dist-info}/WHEEL +0 -0
- {lite_kits-0.1.1.dist-info → lite_kits-0.3.2.dist-info}/entry_points.txt +0 -0
@@ -1,143 +1,143 @@
|
|
1
|
-
---
|
2
|
-
description: Perform security analysis on dependencies and code patterns
|
3
|
-
---
|
4
|
-
|
5
|
-
# Security Audit Helper
|
6
|
-
|
7
|
-
**Purpose**: Quick security analysis for AI agents working on features involving authentication, data handling, or external dependencies.
|
8
|
-
|
9
|
-
## Execution Steps
|
10
|
-
|
11
|
-
Execute the following steps to perform a security audit:
|
12
|
-
|
13
|
-
### 1. Detect Project Type and Dependencies
|
14
|
-
|
15
|
-
```bash
|
16
|
-
# Check for Python dependencies
|
17
|
-
ls requirements.txt pyproject.toml setup.py 2>/dev/null
|
18
|
-
|
19
|
-
# Check for Node.js dependencies
|
20
|
-
ls package.json package-lock.json 2>/dev/null
|
21
|
-
|
22
|
-
# Check for Rust dependencies
|
23
|
-
ls Cargo.toml Cargo.lock 2>/dev/null
|
24
|
-
|
25
|
-
# Check for Go dependencies
|
26
|
-
ls go.mod go.sum 2>/dev/null
|
27
|
-
```
|
28
|
-
|
29
|
-
### 2. Run Dependency Vulnerability Scan
|
30
|
-
|
31
|
-
**Python projects**:
|
32
|
-
```bash
|
33
|
-
# Check if pip-audit is available
|
34
|
-
command -v pip-audit >/dev/null 2>&1
|
35
|
-
|
36
|
-
# If available, run scan
|
37
|
-
pip-audit
|
38
|
-
|
39
|
-
# If not available, suggest installation
|
40
|
-
echo "Install pip-audit: pip install pip-audit"
|
41
|
-
```
|
42
|
-
|
43
|
-
**Node.js projects**:
|
44
|
-
```bash
|
45
|
-
# npm audit is built-in
|
46
|
-
npm audit
|
47
|
-
|
48
|
-
# Or use yarn
|
49
|
-
yarn audit
|
50
|
-
```
|
51
|
-
|
52
|
-
**Other languages**: Suggest appropriate tools (cargo audit, go list, etc.)
|
53
|
-
|
54
|
-
### 3. Scan for Common Security Anti-Patterns
|
55
|
-
|
56
|
-
Check source code for security issues:
|
57
|
-
|
58
|
-
```bash
|
59
|
-
# Look for potential hardcoded secrets
|
60
|
-
grep -r "API_KEY\s*=\s*['\"]" src/ 2>/dev/null | head -5
|
61
|
-
grep -r "PASSWORD\s*=\s*['\"]" src/ 2>/dev/null | head -5
|
62
|
-
grep -r "SECRET\s*=\s*['\"]" src/ 2>/dev/null | head -5
|
63
|
-
|
64
|
-
# Look for weak crypto patterns (Python)
|
65
|
-
grep -r "md5\|sha1" src/ 2>/dev/null | head -5
|
66
|
-
|
67
|
-
# Look for SQL injection risks
|
68
|
-
grep -r "execute.*%\|execute.*+" src/ 2>/dev/null | head -5
|
69
|
-
```
|
70
|
-
|
71
|
-
**Common patterns to flag**:
|
72
|
-
- Hardcoded API keys, passwords, tokens
|
73
|
-
- Weak cryptographic algorithms (MD5, SHA1)
|
74
|
-
- SQL string concatenation
|
75
|
-
- Eval/exec with user input
|
76
|
-
- Insecure file permissions
|
77
|
-
|
78
|
-
### 4. Generate Concise Report
|
79
|
-
|
80
|
-
Provide analysis in this format (~150 words max):
|
81
|
-
|
82
|
-
```markdown
|
83
|
-
## Security Audit
|
84
|
-
|
85
|
-
**Dependencies**: N scanned, M vulnerabilities found
|
86
|
-
|
87
|
-
**Vulnerabilities** (if any):
|
88
|
-
- package-name==version: [SEVERITY] - Brief description
|
89
|
-
- Link to advisory for details
|
90
|
-
|
91
|
-
**Code Patterns** (if any):
|
92
|
-
- file.py:line: [PATTERN] - Recommendation
|
93
|
-
|
94
|
-
**Next Action**: [Fix CVE-XXXX / Update package / Review auth code]
|
95
|
-
```
|
96
|
-
|
97
|
-
## Important Notes
|
98
|
-
|
99
|
-
- **Graceful fallbacks**: If audit tools not installed, do basic pattern checks only
|
100
|
-
- **Be concise**: Target <150 words total output
|
101
|
-
- **Prioritize**: Show highest severity issues first
|
102
|
-
- **Avoid false positives**: Note that manual review may be needed
|
103
|
-
- **No dependencies**: Report "No dependencies to audit" gracefully
|
104
|
-
- **Cross-platform**: Use commands available on Windows, macOS, Linux
|
105
|
-
|
106
|
-
## Edge Cases
|
107
|
-
|
108
|
-
- **No dependency files**: "No dependencies found. This appears to be a dependency-free project."
|
109
|
-
- **Tool not installed**: Provide installation command, run basic grep checks
|
110
|
-
- **No vulnerabilities**: "✅ No known vulnerabilities found! Consider reviewing auth/data handling patterns."
|
111
|
-
- **Too many issues**: Sample top 5, note total count
|
112
|
-
|
113
|
-
## Example Output
|
114
|
-
|
115
|
-
```markdown
|
116
|
-
## Security Audit
|
117
|
-
|
118
|
-
**Dependencies**: 12 scanned, 2 vulnerabilities found
|
119
|
-
|
120
|
-
**Vulnerabilities**:
|
121
|
-
- requests==2.25.0: MEDIUM - CVE-2023-32681 (Proxy-Auth header leak)
|
122
|
-
Update to: requests>=2.31.0
|
123
|
-
|
124
|
-
**Code Patterns**:
|
125
|
-
- src/auth.py:42: Hardcoded API key detected
|
126
|
-
- src/db.py:103: SQL string concatenation (injection risk)
|
127
|
-
|
128
|
-
**Next Action**: Update requests package, move API key to environment variables, use parameterized queries
|
129
|
-
```
|
130
|
-
|
131
|
-
```markdown
|
132
|
-
## Security Audit
|
133
|
-
|
134
|
-
**Dependencies**: pip-audit not installed
|
135
|
-
|
136
|
-
**Tool Not Available**:
|
137
|
-
Install pip-audit for vulnerability scanning:
|
138
|
-
`pip install pip-audit`
|
139
|
-
|
140
|
-
**Code Patterns**: Basic grep checks performed, no obvious issues found
|
141
|
-
|
142
|
-
**Next Action**: Install pip-audit and re-run for comprehensive dependency scan
|
143
|
-
```
|
1
|
+
---
|
2
|
+
description: Perform security analysis on dependencies and code patterns
|
3
|
+
---
|
4
|
+
|
5
|
+
# Security Audit Helper
|
6
|
+
|
7
|
+
**Purpose**: Quick security analysis for AI agents working on features involving authentication, data handling, or external dependencies.
|
8
|
+
|
9
|
+
## Execution Steps
|
10
|
+
|
11
|
+
Execute the following steps to perform a security audit:
|
12
|
+
|
13
|
+
### 1. Detect Project Type and Dependencies
|
14
|
+
|
15
|
+
```bash
|
16
|
+
# Check for Python dependencies
|
17
|
+
ls requirements.txt pyproject.toml setup.py 2>/dev/null
|
18
|
+
|
19
|
+
# Check for Node.js dependencies
|
20
|
+
ls package.json package-lock.json 2>/dev/null
|
21
|
+
|
22
|
+
# Check for Rust dependencies
|
23
|
+
ls Cargo.toml Cargo.lock 2>/dev/null
|
24
|
+
|
25
|
+
# Check for Go dependencies
|
26
|
+
ls go.mod go.sum 2>/dev/null
|
27
|
+
```
|
28
|
+
|
29
|
+
### 2. Run Dependency Vulnerability Scan
|
30
|
+
|
31
|
+
**Python projects**:
|
32
|
+
```bash
|
33
|
+
# Check if pip-audit is available
|
34
|
+
command -v pip-audit >/dev/null 2>&1
|
35
|
+
|
36
|
+
# If available, run scan
|
37
|
+
pip-audit
|
38
|
+
|
39
|
+
# If not available, suggest installation
|
40
|
+
echo "Install pip-audit: pip install pip-audit"
|
41
|
+
```
|
42
|
+
|
43
|
+
**Node.js projects**:
|
44
|
+
```bash
|
45
|
+
# npm audit is built-in
|
46
|
+
npm audit
|
47
|
+
|
48
|
+
# Or use yarn
|
49
|
+
yarn audit
|
50
|
+
```
|
51
|
+
|
52
|
+
**Other languages**: Suggest appropriate tools (cargo audit, go list, etc.)
|
53
|
+
|
54
|
+
### 3. Scan for Common Security Anti-Patterns
|
55
|
+
|
56
|
+
Check source code for security issues:
|
57
|
+
|
58
|
+
```bash
|
59
|
+
# Look for potential hardcoded secrets
|
60
|
+
grep -r "API_KEY\s*=\s*['\"]" src/ 2>/dev/null | head -5
|
61
|
+
grep -r "PASSWORD\s*=\s*['\"]" src/ 2>/dev/null | head -5
|
62
|
+
grep -r "SECRET\s*=\s*['\"]" src/ 2>/dev/null | head -5
|
63
|
+
|
64
|
+
# Look for weak crypto patterns (Python)
|
65
|
+
grep -r "md5\|sha1" src/ 2>/dev/null | head -5
|
66
|
+
|
67
|
+
# Look for SQL injection risks
|
68
|
+
grep -r "execute.*%\|execute.*+" src/ 2>/dev/null | head -5
|
69
|
+
```
|
70
|
+
|
71
|
+
**Common patterns to flag**:
|
72
|
+
- Hardcoded API keys, passwords, tokens
|
73
|
+
- Weak cryptographic algorithms (MD5, SHA1)
|
74
|
+
- SQL string concatenation
|
75
|
+
- Eval/exec with user input
|
76
|
+
- Insecure file permissions
|
77
|
+
|
78
|
+
### 4. Generate Concise Report
|
79
|
+
|
80
|
+
Provide analysis in this format (~150 words max):
|
81
|
+
|
82
|
+
```markdown
|
83
|
+
## Security Audit
|
84
|
+
|
85
|
+
**Dependencies**: N scanned, M vulnerabilities found
|
86
|
+
|
87
|
+
**Vulnerabilities** (if any):
|
88
|
+
- package-name==version: [SEVERITY] - Brief description
|
89
|
+
- Link to advisory for details
|
90
|
+
|
91
|
+
**Code Patterns** (if any):
|
92
|
+
- file.py:line: [PATTERN] - Recommendation
|
93
|
+
|
94
|
+
**Next Action**: [Fix CVE-XXXX / Update package / Review auth code]
|
95
|
+
```
|
96
|
+
|
97
|
+
## Important Notes
|
98
|
+
|
99
|
+
- **Graceful fallbacks**: If audit tools not installed, do basic pattern checks only
|
100
|
+
- **Be concise**: Target <150 words total output
|
101
|
+
- **Prioritize**: Show highest severity issues first
|
102
|
+
- **Avoid false positives**: Note that manual review may be needed
|
103
|
+
- **No dependencies**: Report "No dependencies to audit" gracefully
|
104
|
+
- **Cross-platform**: Use commands available on Windows, macOS, Linux
|
105
|
+
|
106
|
+
## Edge Cases
|
107
|
+
|
108
|
+
- **No dependency files**: "No dependencies found. This appears to be a dependency-free project."
|
109
|
+
- **Tool not installed**: Provide installation command, run basic grep checks
|
110
|
+
- **No vulnerabilities**: "✅ No known vulnerabilities found! Consider reviewing auth/data handling patterns."
|
111
|
+
- **Too many issues**: Sample top 5, note total count
|
112
|
+
|
113
|
+
## Example Output
|
114
|
+
|
115
|
+
```markdown
|
116
|
+
## Security Audit
|
117
|
+
|
118
|
+
**Dependencies**: 12 scanned, 2 vulnerabilities found
|
119
|
+
|
120
|
+
**Vulnerabilities**:
|
121
|
+
- requests==2.25.0: MEDIUM - CVE-2023-32681 (Proxy-Auth header leak)
|
122
|
+
Update to: requests>=2.31.0
|
123
|
+
|
124
|
+
**Code Patterns**:
|
125
|
+
- src/auth.py:42: Hardcoded API key detected
|
126
|
+
- src/db.py:103: SQL string concatenation (injection risk)
|
127
|
+
|
128
|
+
**Next Action**: Update requests package, move API key to environment variables, use parameterized queries
|
129
|
+
```
|
130
|
+
|
131
|
+
```markdown
|
132
|
+
## Security Audit
|
133
|
+
|
134
|
+
**Dependencies**: pip-audit not installed
|
135
|
+
|
136
|
+
**Tool Not Available**:
|
137
|
+
Install pip-audit for vulnerability scanning:
|
138
|
+
`pip install pip-audit`
|
139
|
+
|
140
|
+
**Code Patterns**: Basic grep checks performed, no obvious issues found
|
141
|
+
|
142
|
+
**Next Action**: Install pip-audit and re-run for comprehensive dependency scan
|
143
|
+
```
|
@@ -297,13 +297,13 @@ dev/004-cleanup-command
|
|
297
297
|
$ git branch --merged develop
|
298
298
|
dev/001-starter-kits
|
299
299
|
dev/002-installer-polish
|
300
|
-
dev/003-
|
300
|
+
dev/003-dev-kit-enhancements
|
301
301
|
|
302
302
|
# Agent presents options
|
303
303
|
Merged branches available for cleanup:
|
304
304
|
1. dev/001-starter-kits (2 days ago)
|
305
305
|
2. dev/002-installer-polish (1 day ago)
|
306
|
-
3. dev/003-
|
306
|
+
3. dev/003-dev-kit-enhancements (2 hours ago)
|
307
307
|
|
308
308
|
Delete which branches? (y/n/e): e
|
309
309
|
|
@@ -260,7 +260,7 @@ Message:
|
|
260
260
|
9. ?? docs/new-guide.md
|
261
261
|
|
262
262
|
Message:
|
263
|
-
docs(004): update documentation for
|
263
|
+
docs(004): update documentation for dev-kit
|
264
264
|
|
265
265
|
Added git workflow documentation and updated README
|
266
266
|
with new command examples.
|
@@ -274,7 +274,7 @@ Message:
|
|
274
274
|
Message:
|
275
275
|
chore(004): update implementation status tracking
|
276
276
|
|
277
|
-
Marked
|
277
|
+
Marked dev-kit as complete in status docs.
|
278
278
|
|
279
279
|
---
|
280
280
|
|
@@ -17,8 +17,7 @@ Check for kit marker files to determine what's installed:
|
|
17
17
|
```bash
|
18
18
|
# Check all kits in one command
|
19
19
|
KITS_INSTALLED=""
|
20
|
-
[ -f .claude/commands/orient.md ] && KITS_INSTALLED="${KITS_INSTALLED}
|
21
|
-
[ -f .claude/commands/commit.md ] && KITS_INSTALLED="${KITS_INSTALLED}git "
|
20
|
+
[ -f .claude/commands/orient.md ] && KITS_INSTALLED="${KITS_INSTALLED}dev "
|
22
21
|
[ -f .specify/memory/pr-workflow-guide.md ] && KITS_INSTALLED="${KITS_INSTALLED}multiagent "
|
23
22
|
KITS_INSTALLED="${KITS_INSTALLED:-vanilla only}"
|
24
23
|
```
|
@@ -116,7 +115,7 @@ Based on the state you discovered, suggest the next logical action:
|
|
116
115
|
- **Plan exists, no tasks** → "Run `/tasks` to break down into tasks"
|
117
116
|
- **Tasks exist** → "Run `/implement` to start coding"
|
118
117
|
- **Handoff detected** (multiagent) → "Review handoff in `specs/[feature]/collaboration/active/decisions/`"
|
119
|
-
- **Uncommitted changes** → "Review changes and consider running `/commit`" (if
|
118
|
+
- **Uncommitted changes** → "Review changes and consider running `/commit`" (if dev-kit installed)
|
120
119
|
|
121
120
|
## Important Notes
|
122
121
|
|
@@ -131,7 +130,7 @@ Based on the state you discovered, suggest the next logical action:
|
|
131
130
|
```
|
132
131
|
## Orientation Complete
|
133
132
|
|
134
|
-
**Installed Kits**:
|
133
|
+
**Installed Kits**: dev
|
135
134
|
|
136
135
|
**I am**: claude-sonnet-4.5 @ Claude Code (Primary)
|
137
136
|
**Project**: Blog Platform API (TypeScript/Node.js)
|
@@ -341,7 +341,7 @@ Implements Phase 1 MVP with `/orient` command and modular kit system for multi-a
|
|
341
341
|
## Changes
|
342
342
|
|
343
343
|
### Features
|
344
|
-
- Add `/orient` command for agent orientation (
|
344
|
+
- Add `/orient` command for agent orientation (dev-kit)
|
345
345
|
- Implement kit-aware installer with --kit flag support
|
346
346
|
- Add modular kit structure (project, git, multiagent)
|
347
347
|
- Auto-dependency inclusion (multiagent → project + git)
|