32 lines
998 B
Markdown
32 lines
998 B
Markdown
|
# Task Completion Checklist
|
||
|
|
||
|
When completing any development task in the qenv project, follow these steps:
|
||
|
|
||
|
## Pre-Commit Checks
|
||
|
1. **Run Tests**: `pnpm test`
|
||
|
- Ensure all tests pass
|
||
|
- Add new tests for new functionality
|
||
|
|
||
|
2. **Type Checking**: `pnpm run build`
|
||
|
- Verify no TypeScript errors
|
||
|
- Check that build output is generated correctly
|
||
|
|
||
|
3. **Code Quality**:
|
||
|
- Verify code follows project conventions
|
||
|
- Ensure no console.log statements left in production code
|
||
|
- Check imports use proper .js extensions
|
||
|
|
||
|
## Documentation Updates
|
||
|
- Update README.md if API changes
|
||
|
- Update changelog.md for notable changes
|
||
|
- Ensure JSDoc comments for public APIs
|
||
|
|
||
|
## Final Verification
|
||
|
- Review changes with `git diff`
|
||
|
- Test the module can be imported correctly
|
||
|
- Verify no breaking changes to public API
|
||
|
|
||
|
## Important Notes
|
||
|
- NEVER commit without explicit user approval
|
||
|
- Always run tests and build before suggesting commit
|
||
|
- If lint/typecheck commands unknown, ask user and update CLAUDE.md
|