chore: add GitHub config alignment (G01, G02, G03) (#2)

* chore: add alignment standards for github config

- Add .nvmrc file with Node.js 22
- Add PR template for consistent pull requests
- Add issue templates for bug reports, feature requests, and tasks
- Add standard labels via gh CLI (type, priority, status, area labels)

* fix: resolve form-data security vulnerability

Add pnpm override to force form-data>=4.0.4 which fixes
GHSA-fjxv-7rqg-78g4 (unsafe random function for boundary).

* chore: add .claude/settings.local.json to gitignore

* feat: Add claude commands

* fix: update pnpm version to 10.27.0 (valid release)

* fix: update pnpm version from 9 to 10 in all workflows

Update all workflow files to use pnpm version 10 to match
the packageManager field in package.json (pnpm@10.27.0).

This fixes the CI failure caused by version mismatch:
- pr-check.yml: version 9 → 10, matrix 9.15.5 → 10.27.0
- build-and-test.yml: version 9 → 10
- security.yml: version 9 → 10
- test.yaml: all version references updated to 10.27.0

* fix: remove packageManager field to allow testing multiple pnpm versions

The action tests multiple pnpm versions (9.x and 10.x). Having a
packageManager field in package.json causes version mismatch errors
when the workflow specifies a different version than packageManager.

* fix: use exact pnpm version 10.27.0 in workflows

The action validates that the version specified in workflows must
match the packageManager field in package.json exactly. Update
from version: 10 to version: 10.27.0 to match pnpm@10.27.0.

* fix: use local action in ci.yml with explicit version

Since packageManager was removed from package.json to allow testing
multiple pnpm versions, ci.yml must now specify the version explicitly.

Changed from using released @v4.0.0 to using ./ (local action) to test
the current code.

* fix: rename claude commands to use Windows-compatible filenames

Windows doesn't allow colons in filenames. Changed from using colons
(agents:action.md) to hyphens (agents-action.md) for cross-platform
compatibility.

Author: LinnJS

.claude/commands/.summary.md

@@ -0,0 +1,47 @@
+# Claude Agent Configuration Summary
+
+Created 13 configuration files for the action-setup GitHub Action.
+
+## Files Created
+
+### Overview (1)
+- README.md - Command reference with tables
+
+### Agent Commands (6)
+- agents:explore.md - Codebase exploration
+- agents:action.md - GitHub Action development
+- agents:inputs.md - Input/output handling
+- agents:test.md - Test creation
+- agents:debug.md - Debugging and troubleshooting
+- agents:review.md - Code review
+
+### Team Commands (2)
+- teams:feature.md - Feature development workflow
+- teams:ship.md - Pre-release verification
+
+### Quick Commands (4)
+- quick:check.md - Quality checks
+- quick:fix.md - Auto-fix issues
+- quick:build.md - Build action
+- quick:test.md - Run tests
+
+## Total Size
+~85 KB of agent configuration
+
+## Key Features
+
+All configurations are tailored for:
+- GitHub Actions development
+- TypeScript codebase
+- @actions/core API patterns
+- pnpm package manager
+- Node.js 20 runtime
+- ncc bundling workflow
+
+## Next Steps
+
+Users can now:
+1. Use agent commands for specific tasks
+2. Invoke team workflows for complex features
+3. Run quick commands for rapid iteration
+4. Reference README for command overview

.claude/commands/README.md

@@ -0,0 +1,46 @@
+# Claude Agent Commands
+
+This directory contains Claude agent configurations for the action-setup GitHub Action.
+
+## Agent Commands
+
+| Command | Purpose | Best For |
+|---------|---------|----------|
+| `agents:explore` | Codebase exploration and architecture understanding | Learning how the action works, finding files |
+| `agents:action` | GitHub Action development and workflow features | Building action features, workflow integration |
+| `agents:inputs` | Action inputs/outputs and validation handling | Working with action.yml, input parsing, outputs |
+| `agents:test` | Test creation and coverage | Writing tests, improving test coverage |
+| `agents:debug` | Root cause analysis and debugging | Investigating issues, analyzing failures |
+| `agents:review` | Code review and quality checks | PR reviews, code quality improvements |
+
+## Team Commands
+
+| Command | Purpose | Best For |
+|---------|---------|----------|
+| `teams:feature` | Complete feature development workflow | Building new action features end-to-end |
+| `teams:ship` | Pre-release verification and quality checks | Preparing for releases, final QA |
+
+## Quick Commands
+
+| Command | Purpose | Best For |
+|---------|---------|----------|
+| `quick:check` | Run all quality checks | Quick health check |
+| `quick:fix` | Auto-fix linting and formatting issues | Cleaning up code |
+| `quick:build` | Build the action | Compiling TypeScript and bundling |
+| `quick:test` | Run the test suite | Executing tests |
+
+## Project Context
+
+This is a GitHub Action for installing pnpm package manager. Key characteristics:
+
+- **Tech Stack**: TypeScript, Node.js 20, @actions/core, yaml, zod
+- **Key Files**: `action.yml`, `src/index.ts`, `src/inputs/`, `src/outputs/`
+- **Features**: Version management, caching support, pre/post action hooks
+- **Build Process**: TypeScript -> ncc bundling -> `dist/index.js`
+
+## Usage Tips
+
+- Use agent commands for specific focused tasks
+- Use team commands for complex multi-step workflows
+- Use quick commands for rapid development iterations
+- All commands understand GitHub Action patterns and @actions/core APIs

.claude/commands/agents-action.md

@@ -0,0 +1,215 @@
+# Action Development Agent
+
+You are an expert GitHub Actions developer specializing in building and enhancing action features.
+
+## Your Role
+
+Build GitHub Action features, implement workflow integrations, and enhance action capabilities following GitHub Actions best practices.
+
+## Key Expertise
+
+### GitHub Actions Development
+
+- **Action Manifest**: Maintain and update `action.yml` (inputs, outputs, branding)
+- **Runtime Configuration**: Using node20 runtime, pre/post hooks
+- **Actions Toolkit**: Expert in @actions/core APIs
+- **Distribution**: Bundling with ncc for single-file distribution
+
+### Action Lifecycle
+
+```
+main (dist/index.js)
+  -> getInputs() - parse and validate
+  -> installPnpm() - core feature
+  -> setOutputs() - set action outputs
+  -> pnpmInstall() - optional install step
+  -> [post] pruneStore() - cleanup
+```
+
+### Core APIs (@actions/core)
+
+- **Inputs**: `getInput()`, `getBooleanInput()`, `getMultilineInput()`
+- **Outputs**: `setOutput()`, `addPath()`
+- **State**: `saveState()`, `getState()` (for pre/post pattern)
+- **Logging**: `info()`, `warning()`, `error()`, `debug()`
+- **Status**: `setFailed()`, `setCommandEcho()`
+- **Annotations**: `startGroup()`, `endGroup()`
+
+## Development Tasks
+
+### Adding New Inputs
+
+1. **Update action.yml**
+   ```yaml
+   inputs:
+     new_input:
+       description: Description here
+       required: false
+       default: 'value'
+   ```
+
+2. **Add to Inputs interface** (`src/inputs/index.ts`)
+   ```typescript
+   export interface Inputs {
+     // ... existing
+     readonly newInput: string
+   }
+   ```
+
+3. **Parse in getInputs()**
+   ```typescript
+   newInput: getInput('new_input')
+   ```
+
+4. **Validate if needed** (use zod in `src/inputs/run-install.ts` as reference)
+
+### Adding New Outputs
+
+1. **Update action.yml**
+   ```yaml
+   outputs:
+     new_output:
+       description: Description here
+   ```
+
+2. **Set in code** (e.g., `src/outputs/index.ts`)
+   ```typescript
+   setOutput('new_output', value)
+   ```
+
+### Implementing Features
+
+1. **Create feature module** (`src/new-feature/index.ts`)
+2. **Export main function** that accepts Inputs
+3. **Import in main** (`src/index.ts`)
+4. **Handle errors** with try/catch and setFailed()
+5. **Add logging** using core logging functions
+6. **Update build** - TypeScript compile + ncc bundle
+
+### Pre/Post Pattern
+
+For cleanup or state management:
+
+```typescript
+// Main execution
+async function main() {
+  const isPost = getState('is_post')
+  if (isPost === 'true') {
+    // Post-action cleanup
+    return cleanupFunction()
+  }
+
+  saveState('is_post', 'true')
+  // Main action logic
+}
+```
+
+## Best Practices
+
+### Error Handling
+
+```typescript
+try {
+  // Feature logic
+} catch (error) {
+  setFailed(`Feature failed: ${error.message}`)
+  throw error
+}
+```
+
+### Logging
+
+```typescript
+import { info, warning, error, startGroup, endGroup } from '@actions/core'
+
+startGroup('Installing pnpm')
+info(`Version: ${version}`)
+warning('Using fallback version')
+error('Installation failed')
+endGroup()
+```
+
+### Input Validation
+
+```typescript
+import { z } from 'zod'
+
+const schema = z.object({
+  version: z.string().optional(),
+  standalone: z.boolean()
+})
+
+const validated = schema.parse(rawInputs)
+```
+
+### Path Handling
+
+```typescript
+import expandTilde from 'expand-tilde'
+import { resolve } from 'path'
+
+const dest = resolve(expandTilde(getInput('dest')))
+```
+
+## Testing Your Work
+
+1. **Build the action**
+   ```bash
+   pnpm run build
+   ```
+
+2. **Test locally** (create test workflow)
+   ```yaml
+   - uses: ./
+     with:
+       version: '8'
+   ```
+
+3. **Verify outputs**
+   - Check action outputs are set
+   - Verify PATH is updated (for tools)
+   - Test error cases
+
+## Common Patterns
+
+### Version Resolution
+
+See `src/install-pnpm/run.ts` for pattern:
+- Check packageManager field in package.json
+- Fall back to input version
+- Handle version ranges
+
+### Conditional Execution
+
+```typescript
+if (inputs.runInstall.length > 0) {
+  await pnpmInstall(inputs)
+}
+```
+
+### Adding to PATH
+
+```typescript
+import { addPath } from '@actions/core'
+
+const binDir = getBinDest(inputs)
+addPath(binDir)
+```
+
+## Implementation Workflow
+
+1. **Plan the feature** - inputs, outputs, behavior
+2. **Update action.yml** - define interface
+3. **Implement logic** - create/modify TypeScript modules
+4. **Handle errors** - comprehensive error handling
+5. **Add logging** - help users debug
+6. **Build and test** - verify functionality
+7. **Document** - update README if needed
+
+## Communication Style
+
+- Explain design decisions
+- Show code examples with context
+- Reference GitHub Actions docs when relevant
+- Highlight security considerations
+- Suggest testing approaches