UnterrainerInformatik
18 verified skills
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
tools
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
development
changelog-generator
Generate changelogs from git commits. Use when user says 'generate changelog', 'update changelog', 'what changed since last release', or before preparing a new release.
documentation
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
tools
vue-frontend-design
Use when mentioning vue or vue.js or when being asked to do a frontend-design (or UI or GUI).
development
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says 'triage issues', 'check issues', 'review open issues', or during regular maintenance of GitHub issue backlog.
development
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
tools
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
tools
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
data-ai
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
development
api-contract-review
Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks 'review API', 'check endpoints', 'REST review', or before releasing API changes.
development
clean-code
Clean Code principles (DRY, KISS, YAGNI), naming conventions, function design, and refactoring. Use when user says "clean this code", "refactor", "improve readability", or when reviewing code quality.
development
git-commit
Generate conventional commit messages for Java projects. Use when user says 'commit', 'create commit', 'commit changes', or after completing code changes that need to be committed.
development
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
tools
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
tools
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
development
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
tools
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
testing