Published skills
ai-collaboration-standards
Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty. Keywords: certainty, assumption, inference, evidence, source, 確定性, 推測, 假設, 來源, 證據.
documentation-guide
Guides documentation structure, README content, and project documentation best practices. Apply when creating READMEs, documentation, docs folders, or during project setup.
commit-standards
Formats commit messages following the Conventional Commits standard. Use for writing, committing, and reviewing git history.
requirement-assistant
Guides requirement writing, user story creation, and feature specification. Use when writing requirements, user stories, issues, or planning features.
code-review-assistant
Systematic code review checklist and pre-commit quality gates for Pull Requests. Use when reviewing PRs, checking code quality, and before committing code.
release-standards
Semantic versioning and changelog formatting for software releases. Use when preparing releases, updating version numbers, and writing changelogs.
git-workflow-guide
Guides Git branching strategies, branch naming, and merge operations. Useful for creating branches, merging, pull requests, and Git workflow questions.
testing-guide
Testing pyramid and test writing standards for unit, integration, system, and end-to-end tests. Use when writing tests, discussing test coverage, test strategy, or test naming.
Category alert