Complete Workflow Examples

# Get issue metadata
gh issue view 42 --json title,labels,assignees,state
# Returns: { "title": "Add email validation to registration form", "labels": [{"name": "enhancement"}], "state": "open" }

# Display full issue for user to read
gh issue view 42
# Shows title, body, comments for user review

## Requirements Summary

**Type**: Feature
**Scope**: Add email validation to user registration

### Must Have
- Email format validation (RFC 5322 compliant)
- Return 400 with descriptive error for invalid emails
- Unit tests for validation logic

### Out of Scope
- Email verification via SMTP
- Email normalization

## Verification Summary

### Libraries Verified
- **validator.js** v13.11.0: ✅ Current
  - Notes: Provides `isEmail()` with RFC 5322 compliance

### Quality Checks
- [x] API usage matches official documentation
- [x] No deprecated features in proposed approach

# Find existing validation patterns
grep -r "validation" src/
# Locate registration endpoint
find src -name "*registration*"

# Run test suite
npm test
# PASS: All 127 tests passed

# Run linter
npm run lint
# PASS: No linting errors

# Type checking
npx tsc --noEmit
# PASS: No type errors

# Verify acceptance criteria
- [x] Email validation implemented
- [x] Returns 400 for invalid emails
- [x] Unit tests added and passing

## Test & Quality Report

### Test Results
- Unit tests: ✅ Passed (132/132)
- Integration tests: ✅ Passed (45/45)

### Lint & Static Analysis
- Linter: ✅ No issues
- Type checking: ✅ Passed
- Formatting: ✅ Consistent

### Acceptance Criteria
- [x] Email validation (RFC 5322) — verified
- [x] Returns 400 for invalid emails — verified
- [x] Unit tests added — verified

# Check status
git status --porcelain
# M src/controllers/auth.ts
# M src/utils/validators.ts
# A src/tests/validators.test.ts

# Create branch
git checkout -b "feature/42-add-email-validation"

# Commit
git add -A
git commit -m "feat(validation): add email validation to registration

- Implement RFC 5322 email format validation using validator.js
- Return 400 with descriptive error for invalid emails
- Add unit tests for edge cases (empty string, malformed, valid formats)

Closes #42"

# Push
git push -u origin "feature/42-add-email-validation"

# Detect default branch
TARGET_BRANCH=$(git remote show origin | grep 'HEAD branch' | cut -d' ' -f5)
# main

# Create PR
gh pr create \
    --base main \
    --title "feat(validation): add email validation to registration" \
    --body "## Description

Adds email format validation to the user registration endpoint to prevent invalid email addresses from being stored in the database.

## Changes

- Email format validator using validator.js (RFC 5322 compliant)
- Error response for invalid emails (400 with descriptive message)
- Unit tests covering edge cases (empty, malformed, valid formats)

## Related Issue

Closes #42

## Verification

- [x] All acceptance criteria met
- [x] Tests pass (132/132)
- [x] Code review completed
- [x] No breaking changes"

# Add label
gh pr edit --add-label "enhancement"

# Display PR URL
PR_URL=$(gh pr view --json url -q .url)
# https://github.com/org/repo/pull/145

gh issue view 15 --json title,labels,state
# Returns: { "title": "Login times out after 5 seconds", "labels": [{"name": "bug"}], "state": "open" }

gh issue view 15
# Displays full issue for user review

# Find authentication module
find src -name "*auth*" -o -name "*login*"
# Locate timeout configuration
grep -r "timeout" src/auth/

// Before
const token = await jwt.verify(token, secret, { timeout: 5000 });

// After
const token = await jwt.verify(token, secret, { timeout: config.timeout * 1000 });

# Run tests
npm test
# PASS: All tests passed

# Add regression test
# Test verifies timeout uses milliseconds, not seconds

# Run full suite
npm test
# PASS: 130/130 tests passed

git checkout -b "fix/15-login-timeout"

git add -A
git commit -m "fix(auth): resolve login timeout issue

JWT token verification was using a 5s timeout instead of 30s
due to config value being read in seconds instead of milliseconds.

Root cause: Config timeout (30) was passed directly to jwt.verify()
which expects milliseconds, not seconds.

Fix: Multiply config timeout by 1000 to convert to milliseconds.

Closes #15"

git push -u origin "fix/15-login-timeout"

gh pr create \
    --base main \
    --title "fix(auth): resolve login timeout issue" \
    --body "## Description

Fixes login timeout caused by incorrect timeout unit in JWT verification.

## Root Cause

JWT token verification was configured with a 5-second timeout instead
of the expected 30 seconds because the configuration value (30) was
interpreted as milliseconds instead of seconds.

## Changes

- Fix timeout config to multiply by 1000 (convert seconds to milliseconds)
- Add regression test for timeout configuration
- Add comment explaining timeout unit conversion

## Related Issue

Closes #15

## Verification

- [x] Timeout now uses correct unit (30s instead of 5s)
- [x] Regression test added
- [x] All tests pass (130/130)"

gh issue view 78 --json title,labels
# Returns: { "title": "Improve search performance", "labels": [{"name": "enhancement"}] }

gh issue view 78
# Issue body is vague: "Search is slow, make it faster"

## Requirements Summary

**Type**: Enhancement
**Scope**: Optimize product search performance

### Must Have
- Reduce product search response time from 3-5s to <1s
- Implement database query optimization
- Add caching layer for search results

### Nice to Have
- Search analytics to track slow queries
- Performance monitoring dashboard

### Out of Scope
- User search optimization (separate issue)
- Full-text search reindexing