docs(claude): add gh CLI and commit linting standards (#28)

- Add GitHub Issues quick reference commands
- Add GitHub Issue Dependencies API commands
- Add conventional commit types table
- Add cross-platform and validation requirements
- Add CI/CD workflow expectations
- Add labels reference

Author: CalvinAllen

CLAUDE.md

@@ -4,37 +4,53 @@ This file provides guidance to Claude Code when working with this repository.
 
 ## Critical Rules
 
-1. **NEVER commit directly to main** - Always create a feature branch and submit a pull request
+**These rules override all other instructions:**
+
+1. **NEVER commit directly to main** - Always create a feature branch and submit a pull request. No exceptions.
 2. **Conventional commits** - Format: `type(scope): description`
-3. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues, no local TODO files
-4. **Pull Request titles** - Use conventional commit format
+3. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues, no local TODO files. Use conventional commit format for issue titles
+4. **Pull Request titles** - Use conventional commit format (same as commits)
 5. **Branch naming** - Format: `type/scope/short-description` (e.g., `feat/parser/yaml-support`)
-6. **No co-authors** - Do not add co-author information on commits or pull requests
-7. **No "generated by" statements** - Do not add generated-by statements on pull requests
+6. **Working an issue** - When working an issue, always create a new branch from an updated main branch
+7. **Check branch status before pushing** - ALWAYS verify the remote tracking branch still exists before pushing. If a PR was merged/deleted, create a new branch from main instead of trying to push to the old one.
+8. **Run validation before commits** - Run `cargo fmt`, `cargo clippy`, and `cargo test` before committing and pushing
+9. **Cross-platform** - All features must work on Windows, macOS, and Linux
+10. **No co-authors** - Do not add any co-author information on commits or pull requests
+11. **No "generated by" statements** - Do not add generated-by statements on pull requests
 
-## Project Overview
+---
 
-**rnr** (pronounced "runner") is a cross-platform task runner designed for zero-setup execution. Clone a repo and tasks just work - no dependency installs, no global tools, no configuration.
+## Conventional Commit Types
 
-## Tech Stack
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `refactor` | Code change (no bug fix or feature) |
+| `test` | Adding or updating tests |
+| `chore` | Maintenance tasks |
+| `perf` | Performance improvement |
+| `ci` | CI/CD changes |
+| `build` | Build system or dependencies |
 
-- **Language**: Rust
-- **Target Platforms**: Windows, macOS, Linux
-- **Task File Format**: YAML (`rnr.yaml`)
+---
 
-## Build Commands
+## Quick Reference
+
+### Build Commands
 
 ```bash
 # Build
 cargo build
 
-# Build release
+# Build release (optimized for size)
 cargo build --release
 
 # Run tests
 cargo test
 
-# Run clippy
+# Run clippy (linting)
 cargo clippy
 
 # Format code
@@ -44,6 +60,50 @@ cargo fmt
 cargo run -- <args>
 ```
 
+### GitHub Issues
+
+```bash
+gh issue list                    # List open issues
+gh issue view <number>           # View details
+gh issue create --title "feat(scope): description" --label mvp --body "..."
+gh issue close <number>
+```
+
+### GitHub Issue Dependencies (Blocked By / Blocking)
+
+```bash
+# List what blocks an issue
+gh api repos/CodingWithCalvin/rnr.cli/issues/<number>/dependencies/blocked_by --jq '.[] | "#\(.number) \(.title)"'
+
+# List what an issue blocks
+gh api repos/CodingWithCalvin/rnr.cli/issues/<number>/dependencies/blocking --jq '.[] | "#\(.number) \(.title)"'
+
+# Add a blocking relationship (issue <number> is blocked by <blocker_id>)
+# First get the blocker's numeric ID (not issue number):
+gh api repos/CodingWithCalvin/rnr.cli/issues/<blocker_number> --jq '.id'
+# Then add the dependency:
+gh api repos/CodingWithCalvin/rnr.cli/issues/<number>/dependencies/blocked_by -X POST -F issue_id=<blocker_id>
+
+# Remove a blocking relationship
+gh api repos/CodingWithCalvin/rnr.cli/issues/<number>/dependencies/blocked_by/<blocker_id> -X DELETE
+```
+
+**Note:** The API uses numeric issue IDs (not issue numbers) for POST/DELETE operations. Get the ID with `gh api repos/CodingWithCalvin/rnr.cli/issues/<number> --jq '.id'`
+
+---
+
+## Project Overview
+
+**rnr** (pronounced "runner") is a cross-platform task runner designed for zero-setup execution. Clone a repo and tasks just work - no dependency installs, no global tools, no configuration.
+
+| Attribute | Value |
+|-----------|-------|
+| Language | Rust |
+| Target Platforms | Windows, macOS, Linux |
+| Task File Format | YAML (`rnr.yaml`) |
+
+---
+
 ## Project Structure
 
 ```
@@ -65,6 +125,8 @@ rnr.cli/
 └── README.md
 ```
 
+---
+
 ## Architecture
 
 See `DESIGN.md` for complete design documentation including:
@@ -73,9 +135,9 @@ See `DESIGN.md` for complete design documentation including:
 - MVP features
 - Future features
 
-## Conventions
+---
 
-### Task File Schema
+## Task File Schema
 
 Tasks are defined in `rnr.yaml`:
 
@@ -90,17 +152,65 @@ test:
   env:
     RUST_LOG: debug
   cmd: cargo test
+
+# Sequential steps
+ci:
+  steps:
+    - task: lint
+    - task: test
+    - task: build
+
+# Parallel execution
+build-all:
+  steps:
+    - parallel:
+        - task: build-api
+        - task: build-web
 ```
 
-### Error Handling
+---
 
-- Use `anyhow` for application errors
-- Use `thiserror` for library errors
-- Provide clear, actionable error messages
+## Code Style
 
-### Code Style
+### Rust Conventions
 
 - Follow Rust idioms
 - Use `clippy` for linting
 - Use `rustfmt` for formatting
 - Prefer explicit error handling over `.unwrap()`
+
+### Error Handling
+
+- Use `anyhow` for application errors
+- Use `thiserror` for library errors
+- Provide clear, actionable error messages
+
+### Cross-Platform
+
+- Use `std::path::PathBuf` for paths, not string concatenation
+- Test on Windows, macOS, and Linux
+- Handle platform-specific shell execution (`sh -c` vs `cmd /c`)
+
+---
+
+## CI/CD
+
+### Expected Workflows
+
+| Workflow | Trigger | Purpose |
+|----------|---------|---------|
+| `build.yml` | PR, push to main | Lint, build, test on Windows/macOS/Linux |
+| `release.yml` | Manual/tag | Build release binaries for all platforms |
+| `commit-lint.yml` | PR | Validate PR titles follow conventional commits |
+
+---
+
+## Labels
+
+| Label | Description | Color |
+|-------|-------------|-------|
+| `mvp` | MVP feature | Green |
+| `future` | Future feature | Purple |
+| `core` | Core functionality | Blue |
+| `cli` | CLI commands | Yellow |
+| `build` | Build and distribution | Orange |