Skills

---
name: android-test-writer
description: Writes comprehensive unit and UI tests for Android apps. Use when creating tests, improving test coverage, or debugging test failures.
version: 1.0.0
projectTypes: [android, kotlin]
autoTrigger: true
---

# Android Test Writer

## Unit Tests

Use JUnit 5 with MockK for mocking. Example:

@Test
fun repository returns cached data when available() {
    val cachedUser = User(id = 1, name = "Test")
    every { cache.get("user_1") } returns cachedUser
    
    val result = repository.getUser(1)
    
    assertEquals(cachedUser, result)
    verify(exactly = 0) { api.fetchUser(any()) }
}

## UI Tests

Use Compose Testing for UI verification. Example:

@Test
fun loginScreen_showsErrorOnInvalidCredentials() {
    composeTestRule.setContent {
        LoginScreen(viewModel)
    }
    
    composeTestRule.onNodeWithText("Login").performClick()
    composeTestRule.onNodeWithText("Invalid credentials").assertIsDisplayed()
}

## Best Practices

- Test ViewModels with fake repositories
- Use runTest for coroutine testing
- Mock Android framework dependencies
- Aim for 80%+ coverage on business logic

---
name: database-query
description: Generates SQL queries and analyzes database schemas. Use when working with databases, writing queries, or optimizing database performance.
version: 1.0.0
autoTrigger: true
---

# Database Query Helper

## Schema

Current database schema is documented in [schema.md](schema.md).

## Query Guidelines

### Performance
- Always use indexes for WHERE clauses
- Avoid SELECT * in production
- Use EXPLAIN ANALYZE for complex queries

### Android Room

Example query:

@Query("SELECT * FROM users WHERE age > :minAge ORDER BY name ASC")
suspend fun getUsersOlderThan(minAge: Int): List<User>

### Common Patterns

See [examples.md](examples.md) for:
- Pagination queries
- Join optimization
- Transaction patterns

---
name: commit-helper
description: Generates clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or before committing code.
version: 1.0.0
autoTrigger: true
---

# Commit Message Helper

## Process

1. Run git diff --staged to see changes
2. Analyze the changes:
   - What components are affected?
   - What functionality changed?
   - Why was this change needed?
3. Generate commit message in conventional format

## Format

type(scope): subject

body

footer

## Types
- feat: New feature
- fix: Bug fix
- refactor: Code restructuring
- perf: Performance improvement
- test: Adding tests
- docs: Documentation changes
- chore: Build/tooling changes

## Rules
- Subject line: 50 chars max, present tense
- Body: Explain what and why, not how
- Reference issues in footer: Fixes #123

## Example

feat(auth): add biometric authentication

Implement fingerprint and face recognition for login.
Users can now authenticate using device biometrics as
an alternative to password entry.

- Add BiometricPrompt integration
- Update AuthViewModel with biometric flow
- Add fallback to password on biometric failure

Fixes #456

---
name: pr-reviewer
description: Reviews pull requests for code quality, security issues, and best practices. Use when reviewing PRs, analyzing code changes, or before approving merge requests.
version: 1.0.0
autoTrigger: true
projectTypes: [android, kotlin]
---

# Pull Request Reviewer

## Review Checklist

### Code Quality
- [ ] Functions are focused and single-purpose
- [ ] Variable names are descriptive
- [ ] No code duplication
- [ ] Proper error handling

### Android Specific
- [ ] No memory leaks (lifecycle-aware components)
- [ ] Proper thread handling (coroutines, not blocking)
- [ ] UI updates on main thread
- [ ] Resources properly released

### Security
- [ ] No hardcoded secrets or API keys
- [ ] Input validation on user data
- [ ] SQL injection prevention (use parameterized queries)
- [ ] Proper permission checks

### Testing
- [ ] Unit tests for business logic
- [ ] UI tests for critical flows
- [ ] Edge cases covered

### Performance
- [ ] No unnecessary object creation in loops
- [ ] Efficient list rendering (lazy loading)
- Image loading optimized (Coil caching)

## Review Process

1. Read the PR description and linked issues
2. Check git diff main...HEAD for all changes
3. Review each file systematically
4. Run tests: ./gradlew test
5. Build and run app if UI changes
6. Provide specific, actionable feedback

## Feedback Template

**Strengths:**
- [What's done well]

**Issues:**
- [Critical issues that block merge]

**Suggestions:**
- [Optional improvements]