Strict development workflow for the Minecraft Mod Manager CLI tool. Enforces conventional commits, 100% test coverage, CI verification, and rigorous code quality standards for TypeScript-based Minecraft mod management.
This skill enforces strict development practices for the Minecraft Mod Manager project - a TypeScript CLI tool for managing Minecraft mods from Modrinth and CurseForge.
Guides AI agents to follow rigorous development standards including:
**ALL commits MUST follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).**
- `feat: add new mod scanning functionality`
- `fix: resolve version check error handling`
- `test: add comprehensive tests for config validation`
- `docs: update README with new installation steps`
**Action**: ALWAYS format commit messages using this specification. Reject any commits that don't follow this format.
**ALWAYS run `pnpm run ci` before completing any changes.**
This command executes:
**Action**: Execute `pnpm run ci` after making changes and before committing. If CI fails, fix all issues before proceeding.
**100% test coverage is mandatory - no exceptions.**
**Action**: Before implementing any feature:
1. Write tests first (TDD approach preferred)
2. Ensure 100% line, branch, and function coverage
3. If you think a test should be removed, STOP and ask for guidance
#### File Organization Rules
**CRITICAL**: Respect the architectural separation:
#### Console Output Rules (STRICT)
**Action**: When adding logging:
1. Check file location
2. If in `src/actions/`, use `console.log` or `console.error`
3. If in `src/lib/`, use `Logger` class
4. Never use console methods outside actions
#### Software Hygiene Checklist
**Action**: When adding dependencies:
1. Verify it's truly needed
2. Use `pnpm add <package>`
3. Document why the dependency is required
**Action**:
1. Run `pnpm lint:ci` before committing
2. Fix all linting errors
3. If you don't understand a rule violation, ask for help
**Action**: For each feature:
1. Update inline code documentation
2. Update README.md if user-facing
3. Create/update ADR if architectural decision made
#### Test Structure
#### Test Categories
#### Coverage Requirements
**Action**: When writing tests:
1. Use descriptive test names (e.g., `it('should throw error when config file is missing')`)
2. Test all code paths
3. Use jest-chance for generating varied test data
4. Run `pnpm report` to verify coverage
Follow this workflow strictly:
1. **Before starting**: Run `pnpm ci` to ensure baseline passes
2. **Write tests first**: Follow TDD principles where possible
3. **Implement changes**: Make minimal, focused changes
4. **Verify continuously**: Run `pnpm ci` frequently during development
5. **Commit with conventional messages**: Follow commit format strictly
6. **Final verification**: Ensure `pnpm ci` passes before submitting
#### Minecraft Mod Management Features
#### Configuration Files
#### External APIs
Before creating any pull request:
**DO NOT make assumptions or guess.** Instead:
1. Research the existing codebase for similar patterns
2. Check the ADR documentation in `doc/adr/`
3. Review the README.md and CONTRIBUTING.md
4. Ask for clarification from the team
**Never make things up or implement solutions without understanding requirements.**
```bash
pnpm ci
git checkout -b feat/add-mod-search
pnpm test
pnpm ci
git add .
git commit -m "feat: add mod search functionality"
pnpm ci
git push origin feat/add-mod-search
```
These are requirements, not suggestions. Adherence is mandatory for all contributions.
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/minecraft-mod-manager-development-standards/raw