Skip to content

Claude Skills by AsiaOstrich

github.com/AsiaOstrich

272 skillsA× 256B× 160 installs398 views

Requirement AssistantA[UDS] Write user stories and requirements that satisfy the INVEST criteria. Use when: turning a feature idea into a user story, defining testable acceptance criteria, checking a backlog item for quality. Not for: full specification documents with design and delta operations — use /sdd; deciding whether the idea is right at all — use /brainstorm. Keywords: requirement, user story, INVEST, acceptance criteria, backlog refinement, 需求, 使用者故事, 驗收條件.developmentgoVotes: 0GitHub stars: 75
Retrospective AssistantA[UDS] Guide structured team retrospectives for Sprint and Release cycles. Use when: sprint end, release post-mortem, iteration review, process improvement. Not for: post-mortems for a production incident — use /incident; tracking metric trends between retros — use /metrics. Keywords: retrospective, retro, sprint review, lessons learned, action items.developmentgitVotes: 0GitHub stars: 75
Reverse EngineerA[UDS] System archeology — reverse engineer an existing system across the Logic, Data, and Runtime dimensions. Use when: documenting an undocumented system, recovering specifications from existing code, mapping an unknown data model or runtime topology. Not for: assessing health and risk before a feature — use /discover; deriving tests forward from an approved spec — use /spec-derive. Keywords: reverse engineering, system archeology, legacy code, spec extraction, data model, runtime, 反向工程, 系統考...developmentbashsqlVotes: 0GitHub stars: 75
Runbook AssistantAGuide runbook creation, maintenance, and drill exercises. Use when: writing runbooks, planning drills, auditing runbook coverage, post-incident runbook updates. Not for: responding to an incident already in progress — use /incident; the deployment procedure itself — use /deploy. Keywords: runbook, operations, drill, on-call, procedure.developmentbashapiVotes: 0GitHub stars: 75
Security AssistantAGuide security review and vulnerability assessment following OWASP standards. Use when: security audit, vulnerability check, secure coding review, threat modeling. Not for: automated dependency, CVE, and secret scanning — use /scan; handling a breach in progress — use /incident. Keywords: security, OWASP, vulnerability, authentication, authorization.developmentrustgoVotes: 0GitHub stars: 75
Security Scan AssistantAGuide automated security scanning, dependency auditing, and secret detection. Use when: dependency audit, CVE scanning, secret detection, license compliance. Not for: manual threat modeling and secure design review — use /security; general code cleanliness — use /sweep. Keywords: scan, audit, CVE, dependency, secret, SBOM, vulnerability.developmentbashsqlVotes: 0GitHub stars: 75
Skill BuilderA[UDS] Turn a repeated manual process into a properly scoped Skill, with the right amount of process along the way. Use when: the same multi-step sequence has been done manually three or more times, formalising an ad-hoc Skill, deciding where a Skill belongs. Not for: recording historical facts or project state — that belongs in memory, not a Skill; one-off tasks that will not recur. Keywords: skill, skill builder, process knowledge, repeated process, automation, 技能建立, 流程知識, 自動化.developmentbashgitVotes: 0GitHub stars: 75
Slo AssistantAGuide SLI selection, SLO setting, and Error Budget management. Use when: defining service quality targets, setting up SLO-based alerting, Error Budget policy. Not for: instrumentation and metric collection — use /observability; responding to an active breach of the target — use /incident. Keywords: SLI, SLO, SLA, Error Budget, burn rate, service level.developmentbashapiVotes: 0GitHub stars: 75
Spec DerivationA[UDS] Derive BDD scenarios, TDD skeletons, integration and E2E tests, and ATDD tables from an approved specification. Use when: a spec has been approved and needs test artifacts, generating tagged test skeletons from acceptance criteria, producing contract stubs from a spec. Not for: recovering a spec from existing code — use /reverse; writing or reviewing the spec itself — use /sdd. Keywords: forward derivation, spec to test, BDD scenario, TDD skeleton, ATDD table, 正向推演, 規格衍生, 測試生成.developmentcode-reviewVotes: 0GitHub stars: 75
Spec Driven DevA[UDS] Create and review specification documents before writing code — spec format, states, and delta operations. Use when: a change needs a written spec first, reviewing a spec for completeness, amending an existing spec with delta sections. Not for: executing a gated SDD lifecycle — that moved to the adoption layer (XSPEC-095); lightweight micro-specs for rapid iteration — use the uds spec command. Keywords: SDD, spec, specification, design document, delta operation, spec review, 規格驅動開發, 規格文...developmentgobashVotes: 0GitHub stars: 75
SweepAScan codebase for debug artifacts and code quality issues; optionally auto-fix safe patterns. Use when: before committing, during PR review, or periodic codebase cleanup. Not for: structural code improvement — use /refactor; security-specific scanning — use /scan. Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality.developmenttypescriptbashVotes: 0GitHub stars: 75
Tdd AssistantA[UDS] Reference for Test-Driven Development: the Red-Green-Refactor cycle, FIRST principles, and Arrange-Act-Assert structure. Use when: writing a failing test before implementation, structuring a test with Arrange-Act-Assert, checking tests against FIRST. Not for: driving the RED/GREEN cycle interactively — that moved to the adoption layer (XSPEC-095); measuring how much code the tests cover — use /coverage. Keywords: TDD, test first, Red Green Refactor, FIRST, Arrange Act Assert, unit test,...developmentbashcode-reviewVotes: 0GitHub stars: 75
Test Coverage AssistantA[UDS] Analyze code-level test coverage across the eight-dimension framework and recommend which gaps to close. Use when: coverage percentages look healthy but defects still ship, judging test completeness beyond line percentage, setting coverage targets. Not for: requirement-level AC-to-test traceability — use /ac-coverage; writing the missing tests — use /tdd or /spec-derive. Keywords: test coverage, eight dimensions, line coverage, branch coverage, test quality, 測試覆蓋率, 八維度, 測試完整性.developmentbashVotes: 0GitHub stars: 75
Testing GuideATesting 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. Not for: driving a Red-Green-Refactor cycle — use /tdd; measuring achieved coverage — use /coverage. Keywords: test, unit, integration, e2e, coverage, mock, ISTQB, SIT.developmenttypescriptpythonVotes: 0GitHub stars: 75
Ai Collaboration StandardsAPrevent 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, 確定性, 推測, 假設, 來源, 證據.developmentgitapiVotes: 0GitHub stars: 43
Code Review AssistantASystematic 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, commit, 審查, 檢查, 簽入.developmentgosqlVotes: 0GitHub stars: 43
Commit StandardsAFormat commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refactor.developmentgonodeVotes: 0GitHub stars: 43
Documentation GuideAGuide documentation structure, README content, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.developmentjavascripttypescriptVotes: 0GitHub stars: 43
Git Workflow GuideAGuide 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, 分支, 合併, 工作流程.developmentgobashVotes: 0GitHub stars: 43
Release StandardsASemantic versioning and changelog formatting for software releases. Use when: preparing releases, updating version numbers, writing changelogs. Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.developmentgobashVotes: 0GitHub stars: 43
Requirement AssistantAGuide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.developmentgogitVotes: 0GitHub stars: 43
Testing GuideATesting 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, 測試, 單元, 整合, 端對端.developmenttypescriptpythonVotes: 0GitHub stars: 43