majiayu000/claude-skill-registry-data/pr-writing-majiayu000-claude-skill-registr

#<issue-number> <type>: <concise description>

#42 feat: Add user registration endpoint
#187 fix: Prevent duplicate form submissions
#23 refactor: Extract authentication logic into service
#91 docs: Add API documentation for user endpoints

Update code                    # Too vague, no issue number
Fixed the bug                  # Which bug? No issue number
WIP                           # Not ready for review
feat: Add login               # Missing issue number prefix

## Summary
[1-3 sentences explaining WHAT changed and WHY]
 
Closes #<issue-number>
 
## Changes
-[Specific change 1]
-[Specific change 2]
-[Specific change 3]
 
## Testing
-[ ] Unit tests added/updated
-[ ] Integration tests pass
-[ ] Manual testing completed
 
## Screenshots (if UI changes)
[Before/after screenshots or GIFs]
 
## Notes for Reviewers
[Optional: Areas to focus on, known limitations, questions]

## Changes
 
### API
-Add `POST /api/users/register` endpoint
-Add request validation middleware
-Add rate limiting (10 requests/minute)
 
### Database
-Add `email_verified` column to users table
-Add index on `email` column
 
### Tests
-Add unit tests for registration validation
-Add integration tests for registration flow

## Changes
-Increase connection pool size from 10 to 25
  -Load testing showed connection exhaustion under peak traffic
-Add retry logic to external API calls
  -The payment provider has occasional 503s that resolve on retry

Closes #123

Related to #123
Part of #123

## Notes for Reviewers
 
**Please focus on:**
-The caching invalidation logic in `src/cache/manager.ts` - I'm unsure if this handles all edge cases
-The error handling in the new endpoint
 
**You can skim:**
-The test files follow existing patterns
-The migration is straightforward

## Screenshots
 
### Before
[screenshot]
 
### After
[screenshot]

## User Flow
 
1.User clicks "Register"
   [screenshot 1]
 
2.Validation errors shown inline
   [screenshot 2]
 
3.Success state with redirect
   [screenshot 3]

## ⚠️ Breaking Changes
 
-`getUserById()` now returns `null` instead of throwing when user not found
-The `/api/v1/users` endpoint is deprecated, use `/api/v2/users`
 
### Migration Guide
1.Update all `try/catch` blocks around `getUserById()` to null checks
2.Update API clients to use v2 endpoint

## 🚧 Draft PR
 
This is a draft to get early feedback on the approach.
 
**Questions:**
1.Should we use Redis or in-memory caching?
2.Is this the right place for this logic?
 
**Not yet complete:**
-[ ] Error handling
-[ ] Tests
-[ ] Documentation

## Note on PR Size
 
This PR is larger than usual because it includes a database migration
that requires updating all affected queries atomically. Splitting would
leave the codebase in a broken state.