claudeforge-cli 1.0.3 → 1.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudeforge-cli",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "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

@@ -10,17 +10,17 @@ Do not ask the user for a description. Read the codebase directly to infer every
 ### 1a. Project identity
 
 !`ls -la`
-!`cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat go.mod 2>/dev/null || cat Cargo.toml 2>/dev/null || echo "(no manifest found)"`
-!`cat README.md 2>/dev/null | head -60 || echo "(no README)"`
+!`test -f package.json && cat package.json || test -f pyproject.toml && cat pyproject.toml || test -f go.mod && cat go.mod || test -f Cargo.toml && cat Cargo.toml || echo "(no manifest found)"`
+!`test -f README.md && head -60 README.md || echo "(no README)"`
 
 ### 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`
+!`test -f package.json && cat package.json || echo "(no package.json)"`
+!`test -f requirements.txt && cat requirements.txt || test -f pyproject.toml && cat pyproject.toml || echo "(no python deps)"`
+!`test -f go.mod && cat go.mod || echo "(no go.mod)"`
+!`test -f Cargo.toml && cat Cargo.toml || echo "(no Cargo.toml)"`
+!`test -f pom.xml && head -80 pom.xml || echo "(no pom.xml)"`
+!`test -f Gemfile && cat Gemfile || echo "(no Gemfile)"`
 
 ### 1c. Project structure
 
@@ -48,17 +48,17 @@ 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 --oneline -20 || echo "(no git history)"`
+!`git log --pretty=format:"%s" -50 | 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)"`
-!`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)"`
+!`test -d .github/workflows && find .github/workflows -name "*.yml" | head -5 | xargs head -100 || echo "(no GitHub Actions)"`
+!`test -f Dockerfile && head -40 Dockerfile || echo "(no Dockerfile)"`
+!`test -f docker-compose.yml && cat docker-compose.yml || echo "(no docker-compose)"`
+!`test -f .env.example && cat .env.example || test -f .env.sample && cat .env.sample || echo "(no .env.example)"`
 
 ---