@etus/bhono-app 0.1.1

package/templates/base/.claude/commands/linear/setup.md

@@ -0,0 +1,180 @@
+---
+description: Initialize Linear configuration for this project - setup credentials, default team, project, and preferences
+---
+
+# Linear Setup for Project
+
+Execute the following setup workflow step by step:
+
+## Step 1: Verify Credentials
+
+Check if Linear credentials are configured:
+- Try to execute: `cd .claude/skills/linear && npx tsx scripts/list-teams.ts --json`
+- If it fails with "LINEAR_API_KEY not found":
+  - Tell user: "Linear API key not found. Running credential setup..."
+  - Execute: `cd .claude/skills/linear && npx tsx scripts/setup/setup-credentials.ts`
+  - Wait for completion before proceeding
+
+## Step 2: Get Current User
+
+Use the linear skill to get current user information:
+- Execute: `cd .claude/skills/linear && npx tsx scripts/users/me.ts --json`
+- Extract and display: user name and email
+- Save user ID for later use
+
+## Step 3: List Available Teams
+
+Use the linear skill to list all teams:
+- Execute: `cd .claude/skills/linear && npx tsx scripts/list-teams.ts --json`
+- Display teams in a clear format showing: name, key, and ID
+- Ask user: "Which team should be the default for this project?"
+- Use AskUserQuestion tool to let user select from the list
+- Save selected team ID and name
+
+## Step 4: List Projects for Selected Team
+
+Use the linear skill to list projects for the selected team:
+- Filter projects from step 3 that match the selected team ID
+- Display projects showing: name and ID
+- Ask user: "Which project should issues be associated with by default?"
+- Options: List all projects + "None (no default project)"
+- Use AskUserQuestion tool to let user select
+- Save selected project ID (or null if "None")
+
+## Step 5: Auto-Assignment Preference
+
+Ask user about auto-assignment:
+- Use AskUserQuestion tool with options:
+  - "Yes - Always assign new issues to me"
+  - "No - Leave issues unassigned by default"
+- Save preference (true/false)
+
+## Step 6: Configuration Sharing Preference
+
+Explain to the user:
+```
+📋 Configuration Storage
+
+Your Linear preferences will be saved to: .claude/linear-config.json
+
+This file contains:
+- Default team and project for this repository
+- Your auto-assignment preference
+- Your user information
+
+You have two options:
+```
+
+Use AskUserQuestion tool:
+- Question: "How should this configuration be handled?"
+- Header: "Config Sharing"
+- Options:
+  - "Commit to git - Share defaults with team (recommended for team projects)"
+  - "Keep local only - Add to .gitignore (recommended for personal projects)"
+
+**If "Commit to git"**:
+- Configuration will be committed and shared with team
+- Everyone cloning the repo will use these defaults
+- Note: User information is personal but safe to share
+
+**If "Keep local only"**:
+- Add `.claude/linear-config.json` to `.gitignore` if not already there
+- Each team member will need to run setup
+- More flexible for teams using different teams/projects
+
+Save the user's choice for the next step.
+
+## Step 7: Save Configuration
+
+Create configuration file at `.claude/linear-config.json` with structure:
+```json
+{
+  "user": {
+    "id": "<user-id>",
+    "name": "<user-name>",
+    "email": "<user-email>"
+  },
+  "defaults": {
+    "teamId": "<selected-team-id>",
+    "teamName": "<selected-team-name>",
+    "teamKey": "<selected-team-key>",
+    "projectId": "<selected-project-id-or-null>",
+    "projectName": "<selected-project-name-or-null>",
+    "autoAssign": true/false
+  },
+  "setupDate": "<current-date-iso>"
+}
+```
+
+Use the Write tool to create this file with proper JSON formatting.
+
+**If user chose "Keep local only"**:
+- Check if `.gitignore` exists in project root
+- If `.gitignore` exists:
+  - Check if `.claude/linear-config.json` is already ignored
+  - If not, append: `.claude/linear-config.json` to `.gitignore`
+  - Confirm: "Added .claude/linear-config.json to .gitignore"
+- If `.gitignore` doesn't exist:
+  - Tell user: "⚠️  No .gitignore found. Remember to add .claude/linear-config.json manually if you don't want to commit it."
+
+**If user chose "Commit to git"**:
+- Do nothing extra
+- Configuration will be available for git commit
+
+## Step 8: Confirmation
+
+Display success message with configuration details and sharing status:
+
+**If user chose "Commit to git"**:
+```
+✅ Linear configuration completed!
+
+📋 Configuration Details:
+Default Team: <team-name> (<team-key>)
+Default Project: <project-name or "None">
+Auto-assign: <Yes/No>
+User: <user-name> (<user-email>)
+
+📁 Configuration saved to: .claude/linear-config.json
+🔄 Sharing: Will be committed to git (shared with team)
+
+Next steps:
+• Commit this file to share defaults with your team
+• Use /linear:create-issue to create issues
+• Run /linear:setup again to reconfigure
+```
+
+**If user chose "Keep local only"**:
+```
+✅ Linear configuration completed!
+
+📋 Configuration Details:
+Default Team: <team-name> (<team-key>)
+Default Project: <project-name or "None">
+Auto-assign: <Yes/No>
+User: <user-name> (<user-email>)
+
+📁 Configuration saved to: .claude/linear-config.json
+🔒 Privacy: Local only (added to .gitignore)
+
+Next steps:
+• Your preferences are personal and won't be committed
+• Team members will need to run /linear:setup
+• Use /linear:create-issue to create issues
+• Run /linear:setup again to reconfigure
+```
+
+## Error Handling
+
+- If any step fails, display clear error message
+- If credentials setup fails, provide instructions to manually configure ~/.linear/credentials
+- If user cancels during questions, save partial config and explain what's missing
+- Always verify each Linear API call succeeded before proceeding
+
+## Important Notes
+
+- Execute each step sequentially, waiting for completion
+- Use AskUserQuestion for all user choices (don't guess)
+- Validate all IDs exist before saving to config
+- Create .claude directory if it doesn't exist
+- Make config file readable with proper formatting

package/templates/base/.claude/commands/prime.md

@@ -0,0 +1,9 @@
+# Prime
+
+> Execute the following sections to understand the codebase then summarize your understanding.
+
+## Run these commands to prime the context
+
+!`git ls-files | grep -v -E '^(dist/|\.wrangler/|\.claude/|\.cursor/|\.factory/|\.github/|playwright-report/|tests/|docs/|node_modules/)' && git ls-files docs/architecture/ docs/features/ docs/tech-specs/ docs/sdlc/ docs/runbooks/ docs/data/'`
+!`git log --oneline -20`
+!`cat README.md`

package/templates/base/.claude/commands/review-gap.md

@@ -0,0 +1,10 @@
+# Review Previous Task
+
+Review the previous task and search for gaps during the execution of the task and errors that could be made during the execution of the task.
+
+## Instructions
+
+1. Review the previous task and provide a detailed analysis of the task.
+2. Identify the gaps in the task.
+3. Provide a detailed plan to address the gaps.
+4. Fix the errors that could be made during the execution of the task.

package/templates/base/.claude/commands/setup-aa.md

@@ -0,0 +1,311 @@
+---
+description: Implement the AA Setup for IA with all the Agents, Skills, Commands, and other configurations(statusline, settings.json, hooks)
+tags: [project, setup, configuration, statusline, hooks]
+---
+
+# Setup AA for IA
+
+Run interactive setup to configure your Claude Code project with optimal settings.
+
+## Pre-Setup Analysis
+
+Before running setup, analyze current configuration:
+
+**Steps:**
+
+1. Check if `.claude/settings.json` exists
+2. Check if `.claude/hooks/hooks.json` is properly configured
+3. Check if statusline is configured
+4. Check current VERSION
+5. Present summary to user with recommendations
+
+**Present findings like:**
+
+```
+🔍 Current Configuration Status:
+
+✅ settings.json: Exists (needs review)
+⚠️  hooks.json: Missing SessionStart hooks
+❌ statusline: Not configured
+✅ VERSION: 1.0.1
+
+Recommendations:
+- Add SessionStart automation hooks
+- Configure statusline for better visibility
+- Review settings.json permissions
+```
+
+## Ask User for Setup Preferences
+
+After analysis, ask user what they want to configure:
+
+**Question:** "What would you like to setup?"
+
+**Options:**
+
+1. **Full Setup** - Configure everything (settings.json, hooks, statusline)
+2. **Hooks Only** - Just add/update SessionStart automation hooks
+3. **Statusline Only** - Just configure statusline
+4. **Review Only** - Show current config without changes
+5. **Custom** - Let me choose specific items
+
+## Execution Based on User Choice
+
+### Option 1: Full Setup
+
+1. **Backup existing files:**
+
+   - Create `settings.json.backup.[timestamp]`
+   - Show backup path to user
+
+2. **Run setup script:**
+
+   ```bash
+   ./.claude/scripts/setup-project.sh
+   ```
+
+3. **Verify results:**
+
+   - Check if settings.json was created/updated
+   - Check if hooks are configured
+   - Check if statusline is working
+
+4. **Show summary:**
+
+   ```
+   ✅ Setup Complete!
+
+   Configured:
+   - ✅ settings.json (with optimal permissions)
+   - ✅ SessionStart hooks (install_pkgs, validate-skill-rules, check-updates)
+   - ✅ UserPromptSubmit hook (skill activation)
+   - ✅ Statusline (git branch + model info)
+
+   Next steps:
+   1. Review .claude/settings.json
+   2. Restart Claude Code to activate changes
+   3. Test with: "list available skills"
+   ```
+
+### Option 2: Hooks Only
+
+1. **Read current hooks.json:**
+
+   ```bash
+   cat .claude/hooks/hooks.json
+   ```
+
+2. **Check what's missing:**
+
+   - UserPromptSubmit hook?
+   - SessionStart hooks?
+   - Which specific hooks are missing?
+
+3. **Update hooks.json** to include:
+
+   ```json
+   {
+   	"hooks": {
+   		"UserPromptSubmit": [
+   			{
+   				"hooks": [
+   					{
+   						"type": "command",
+   						"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/skill-activation-prompt.sh"
+   					}
+   				]
+   			}
+   		],
+   		"SessionStart": [
+   			{
+   				"matcher": "startup",
+   				"hooks": [
+   					{
+   						"type": "command",
+   						"command": "$CLAUDE_PROJECT_DIR/.claude/scripts/install_pkgs.sh"
+   					},
+   					{
+   						"type": "command",
+   						"command": "$CLAUDE_PROJECT_DIR/.claude/scripts/validate-skill-rules.sh"
+   					},
+   					{
+   						"type": "command",
+   						"command": "$CLAUDE_PROJECT_DIR/.claude/scripts/check-updates.sh"
+   					}
+   				]
+   			}
+   		]
+   	}
+   }
+   ```
+
+4. **Validate JSON syntax:**
+   ```bash
+   cat .claude/hooks/hooks.json | jq . > /dev/null && echo "✅ Valid JSON"
+   ```
+
+### Option 3: Statusline Only
+
+1. **Check if statusline exists in settings.json:**
+
+   ```bash
+   jq 'has("statusLine")' .claude/settings.json
+   ```
+
+2. **If missing, add statusline configuration:**
+
+   - Backup settings.json first
+   - Add this statusLine config:
+
+   ```json
+   "statusLine": {
+     "type": "command",
+     "command": "bash -c 'input=$(cat); MODEL=$(echo \"$input\" | jq -r \".model.display_name\"); DIR=$(echo \"$input\" | jq -r \".workspace.current_dir\"); BRANCH=\"\"; if git rev-parse --git-dir >/dev/null 2>&1; then BRANCH=\" | 🌿 $(git branch --show-current 2>/dev/null)\"; CHANGES=$(git status --porcelain 2>/dev/null | wc -l); if [ $CHANGES -gt 0 ]; then BRANCH=\"$BRANCH ($CHANGES)\"; fi; fi; echo \"[$MODEL] 📁 ${DIR##*/}$BRANCH\"'\"
+   }
+   ```
+
+3. **Show preview:**
+
+   ```
+   Statusline will show:
+   [Sonnet 4.5] 📁 ia-setup | 🌿 main (2)
+
+   Where:
+   - [Sonnet 4.5] = Current model
+   - 📁 ia-setup = Current directory
+   - 🌿 main = Git branch
+   - (2) = Number of uncommitted changes
+   ```
+
+### Option 4: Review Only
+
+1. **Show current settings.json** (key sections):
+
+   - env variables
+   - enabled MCP servers
+   - permissions
+   - hooks configuration
+   - statusline
+
+2. **Show current hooks.json:**
+
+   - List all configured hooks
+   - Explain what each does
+
+3. **Show current VERSION:**
+
+   - Current: X.X.X
+   - Check if update available
+
+4. **Provide recommendations** without making changes
+
+### Option 5: Custom
+
+Ask user specifically what they want:
+
+- "Add SessionStart hooks?"
+- "Configure statusline?"
+- "Update permissions in settings.json?"
+- "Add specific MCP servers to enabledMcpjsonServers?"
+
+Then execute only selected items.
+
+## Safety Rules
+
+**ALWAYS:**
+
+- ✅ Create backups before modifying existing files
+- ✅ Show backup path to user
+- ✅ Validate JSON syntax after changes
+- ✅ Show clear summary of what was changed
+- ✅ Provide rollback instructions if something goes wrong
+
+**NEVER:**
+
+- ❌ Overwrite settings.json without backup
+- ❌ Remove existing configuration
+- ❌ Make changes without user confirmation
+- ❌ Proceed if JSON validation fails
+
+## Rollback Instructions
+
+If setup causes issues:
+
+```bash
+# Restore from backup
+cp .claude/settings.json.backup.[timestamp] .claude/settings.json
+
+# Or reset hooks
+git checkout .claude/hooks/hooks.json
+
+# Restart Claude Code
+```
+
+## Post-Setup Verification
+
+After setup, verify everything works:
+
+1. **Test hooks:**
+
+   - Restart Claude Code session
+   - Check if SessionStart hooks executed
+   - Try skill activation: "use brainstorming skill"
+
+2. **Test statusline:**
+
+   - Check bottom of terminal
+   - Should show: `[Model] 📁 dir | 🌿 branch (changes)`
+
+3. **Test MCP servers:**
+
+   ```bash
+   # Check enabled servers
+   jq '.enabledMcpjsonServers' .claude/settings.json
+   ```
+
+4. **Report results to user**
+
+## Example Output
+
+Good output format:
+
+```
+🎯 Claude Code Project Setup Complete!
+
+Changes Made:
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ settings.json
+   - Created with optimal configuration
+   - Enabled: context7, sequential-thinking MCPs
+   - Added comprehensive permissions
+
+✅ Hooks Configuration
+   - UserPromptSubmit: skill-activation-prompt.sh
+   - SessionStart:
+     • install_pkgs.sh (auto-install dependencies)
+     • validate-skill-rules.sh (validate skills)
+     • check-updates.sh (check for updates)
+
+✅ Statusline
+   - Shows: [Model] 📁 dir | 🌿 branch (changes)
+
+📦 Backup Created
+   - Location: .claude/settings.json.backup.1699123456
+
+🔄 Next Steps
+   1. Restart Claude Code to activate changes
+   2. Test skill activation: "use brainstorming"
+   3. Check statusline appears at bottom
+
+💡 Rollback if needed:
+   cp .claude/settings.json.backup.1699123456 .claude/settings.json
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## Notes
+
+- This command wraps the `setup-project.sh` script with better UX
+- Always interactive - never assumes user wants everything
+- Clear communication about what's being changed
+- Easy rollback if something goes wrong
+- Validates all changes before considering setup complete