build-test-auto
Automatically builds and tests code changes. Use whenever code is modified, tests fail, before creating pull requests, or when verifying code quality.
What this skill does
# Automated Build & Test Workflow
## Overview
This skill provides automated build and test execution for various project types. It is triggered automatically when code changes are made or when tests need verification.
## Quick Reference
### Project Detection & Commands
```bash
# JavaScript/Node.js
if [ -f "package.json" ]; then
npm install && npm run build && npm test
fi
# Python
if [ -f "pyproject.toml" ] || [ -f "setup.py" ]; then
pip install -e . && python -m pytest
fi
# Rust
if [ -f "Cargo.toml" ]; then
cargo build && cargo test
fi
# Go
if [ -f "go.mod" ]; then
go build ./... && go test ./...
fi
# Java Maven
if [ -f "pom.xml" ]; then
mvn compile && mvn test
fi
# Java/Kotlin Gradle
if [ -f "build.gradle" ] || [ -f "build.gradle.kts" ]; then
./gradlew build && ./gradlew test
fi
# Ruby
if [ -f "Gemfile" ]; then
bundle install && bundle exec rspec
fi
# Make-based
if [ -f "Makefile" ]; then
make && make test
fi
```
## Workflow Steps
### 1. Pre-Build Checks
- Verify dependencies are installed
- Check for required tools (use `mise` if available)
- Validate configuration files
### 2. Build Phase
- Run the build command
- Capture all output
- Stop immediately on build failure
- Show exact error location
### 3. Test Phase
- Run the full test suite
- Capture test output with verbose mode
- Document all failures
### 4. Failure Analysis
For each failure:
1. Identify the test name and file
2. Show the exact error message
3. Display relevant stack trace
4. Analyze root cause
### 5. Fix & Verify
- Apply minimal fixes
- Re-run tests to confirm
- Report final status
## Linting
After tests pass, also run linting:
| Project Type | Lint Command |
|-------------|--------------|
| Node.js | `npm run lint` |
| Python | `ruff check .` or `flake8` |
| Rust | `cargo clippy` |
| Go | `go vet ./...` |
## Tips
- Use `mise` to install missing runtimes
- Check `.nvmrc`, `.python-version`, `.tool-versions` for version requirements
- Run lint and build before pushing to remote
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.