claudeforge-cli 1.0.3 → 1.0.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudeforge-cli",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "description": "Forge production-ready AI agent projects — agents, slash commands, memory, CI/CD, and devcontainers in one command",
   "bin": {
     "claudeforge": "bin/cli.js"

package/templates/claude/commands/analyze-project.md.tpl

@@ -15,17 +15,17 @@ Do not ask the user for a description. Read the codebase directly to infer every
 
 ### 1b. Full dependency map
 
-!`cat package.json 2>/dev/null`
-!`cat requirements.txt 2>/dev/null || cat pyproject.toml 2>/dev/null`
-!`cat go.mod 2>/dev/null`
-!`cat Cargo.toml 2>/dev/null`
-!`cat pom.xml 2>/dev/null | head -80`
-!`cat Gemfile 2>/dev/null`
+!`cat package.json 2>/dev/null || echo "(no package.json)"`
+!`cat requirements.txt 2>/dev/null || cat pyproject.toml 2>/dev/null || echo "(no python deps)"`
+!`cat go.mod 2>/dev/null || echo "(no go.mod)"`
+!`cat Cargo.toml 2>/dev/null || echo "(no Cargo.toml)"`
+!`cat pom.xml 2>/dev/null | head -80 || echo "(no pom.xml)"`
+!`cat Gemfile 2>/dev/null || echo "(no Gemfile)"`
 
 ### 1c. Project structure
 
-!`find . -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.java" -o -name "*.rb" \) -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/dist/*" -not -path "*/__pycache__/*" -not -path "*/target/*" | head -80`
-!`find . -type d -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/__pycache__/*" -not -path "*/target/*" -not -path "*/dist/*" | head -40`
+!`find . -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.java" -o -name "*.rb" \) -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/dist/*" -not -path "*/__pycache__/*" -not -path "*/target/*" 2>/dev/null | head -80 || echo "(no source files found)"`
+!`find . -type d -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/__pycache__/*" -not -path "*/target/*" -not -path "*/dist/*" 2>/dev/null | head -40 || echo "(no directories found)"`
 
 ### 1d. Read actual source code — infer real patterns
 
@@ -49,13 +49,13 @@ Read enough code to answer:
 ### 1e. Git history — understand how the project evolved
 
 !`git log --oneline -20 2>/dev/null || echo "(no git history)"`
-!`git log --pretty=format:"%s" -50 2>/dev/null | sort | uniq -c | sort -rn | head -20`
+!`git log --pretty=format:"%s" -50 2>/dev/null | sort | uniq -c | sort -rn | head -20 || echo "(no commits)"`
 
 What do the commit messages reveal about the team's workflow and focus areas?
 
 ### 1f. Existing CI/CD and infrastructure
 
-!`cat .github/workflows/*.yml 2>/dev/null | head -100 || echo "(no GitHub Actions)"`
+!`find .github/workflows -name "*.yml" 2>/dev/null | head -5 | xargs cat 2>/dev/null | head -100 || echo "(no GitHub Actions)"`
 !`cat Dockerfile 2>/dev/null | head -40 || echo "(no Dockerfile)"`
 !`cat docker-compose.yml 2>/dev/null || echo "(no docker-compose)"`
 !`cat .env.example 2>/dev/null || cat .env.sample 2>/dev/null || echo "(no .env.example)"`