buildlisted

See `~/.claude/learnings/shell-environment.md` for the expected bash functions and verification checklist. ## Context - Build function in bashrc: !`grep -c "build()" ~/.bashrc 2>/dev/null || echo 0` - Wrapper script exists: !`test -f scripts/build.sh && echo yes || echo no` - Scripts in gitignore: !`grep -cx 'scripts/' .gitignore 2>/dev/null || echo 0` - GitHub workflow: !`ls .github/workflows/*.yml 2>/dev/null || echo none` ## 1. Check prerequisites 1. If **Build function** is 0, append the function to `~/.bashrc`: ```bash build() { if [ -f scripts/build.sh ]; then bash scripts/build.sh "$@"; else echo "No scripts/build.sh in current directory"; fi; } ``` ## 2. Set up quick build shortcut 1. If **Wrapper script exists** is no, create `scripts/build.sh`: ```bash #!/bin/bash bash ~/.claude/skills/build/scripts/build.sh "$@" ``` 2. If **Scripts in gitignore** is 0, append to `.gitignore`: ``` # Local convenience scripts (not committed) scripts/ ``` ## 3. Configure GitHub Actions CI (optional) If **GitHub workflow** is `none`: 1. Ask the user: "No GitHub Actions workflow found. Set up CI for push/PR builds?" 2. If declined, skip to step 4. 3. Detect project type and parameters (see below). 4. Generate the workflow, show it to the user for approval. 5. On approval: `mkdir -p .github/workflows`, then write `.github/workflows/build.yml`. ### Project type detection | Check | How | Type | |---|---|---| | `test -d src-tauri` | directory exist