commit-standards
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refa...
Browse published AI skills maintained by AsiaOstrich. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
61Repository stars across indexed skills
1,518Repository forks
292Average repository stars per indexed skill
25Repository stars may repeat across skills from the same repository.
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refa...
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/ce...
Testing pyramid and test writing standards for UT/IT/ST/E2E. Use when: writing tests, discussing test coverage, test strategy, or test naming. Keywords: test, unit, integration, e2e, coverage, mock, 測試, 單元,...
Guide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specificatio...
Semantic versioning and changelog formatting for software releases. Use when: preparing releases, updating version numbers, writing changelogs. Keywords: version, release, changelog, semver, major, minor, patch...
Guide documentation structure, README content, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup. Keywords: README, docs, documentation, CONTRIBUTING...
Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, c...
Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow,...
Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow,...
Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage, test strategy, or test naming. Keywords: test, uni...
語意化版本控制和變更日誌格式化的軟體發布標準。 使用時機:準備發布、更新版本號、撰寫變更日誌。 關鍵字:version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌。
Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage, test strategy, or test naming. Keywords: test, uni...
依照 Keep a Changelog 格式撰写与維護 CHANGELOG.md。 使用时机:建立变更日誌条目、准备發布、记录变更。 关鍵字:changelog, release notes, CHANGELOG.md, keep a changelog, 变更日誌, 發布说明。
引導文件结构、内容需求和项目文件最佳实踐。 使用时机:建立 README、文件、docs 目录、项目设置、技術文件。 关鍵字:README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文件, 说明文件, 技術...
引導提交前品质关卡和簽入工作流程。 使用时机:提交程序码、准备提交、品质关卡验证。 关鍵字:commit, checkin, pre-commit, quality gate, git add, 提交, 簽入, 品质关卡.
将现有代码反向工程成 SDD 规格文档。 使用时机:分析旧有代码、为未文档化的系统撰写文档、从现有实作提取规格。 关键字:reverse engineering, legacy code, documentation, spec extraction, code archaeology, 反向工程,...
引導需求撰寫、使用者故事建立與功能規格制定。 使用時機:撰寫需求、使用者故事、問題單、功能規劃。 關鍵字:requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格。
Evaluate test completeness using the 8 dimensions framework. Use when: writing tests, reviewing test coverage, ensuring test quality. Keywords: test coverage, completeness, dimensions, 8 dimensions, test qualit...
引导重构决策和大规模代码改进。 使用时机:重构代码、遗留系统现代化、技术债、重写决策。 关键字:refactor, rewrite, legacy, strangler, technical debt, 重构, 重写, 技术债.
Guide teams through Acceptance Test-Driven Development workflow. Use when: defining acceptance criteria, running specification workshops, writing user stories with acceptance tests, PO sign-off. Keywords: ATDD,...
实作结构化日誌,包含正确的日誌层级和敏感数据处理。 使用时机:新增日誌、除錯、设置可觀测性。 关鍵字:logging, log level, structured logging, observability, 日誌, 记录, 结构化日誌。
设计一致的错误码,遵循 PREFIX_CATEGORY_NUMBER 格式。 使用时机:定義错误码、建立错误处理、设计 API。 关鍵字:error code, error handling, error format, API errors, 错误码, 错误处理。
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, feat, fix, refactor.
指導 Git 分支策略、分支命名與合併操作。 使用時機:建立分支、合併、Pull Request、Git 工作流程問題。 關鍵字:branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程。
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.