security
1.2K
authentication-patterns
Authentication and authorization patterns including OAuth2, JWT, RBAC, session management, and PKCE flows
rohitg00
testing-security
sorting
์คํ
current ordering strategy
query
all entries
refine the visible subset
security
1.2K
security-hardening
Application security covering input validation, auth, headers, secrets management, and dependency auditing
rohitg00
testing-security
testing
1.2K
testing-strategies
Testing strategies including contract testing, snapshot testing, mutation testing, property-based testing, and test organization
rohitg00
testing-security
testing
1.2K
testing-standards
Testing conventions for Stock Indicators. Use for test naming (MethodName_StateUnderTest_ExpectedBehavior), FluentAssertions patterns, precision requirements, and test base class selection.
DaveSkender
testing-security
code-quality
1.2K
code-review
Review code changes for architecture, security, conventions, and quality compliance. Use when reviewing pull requests, code changes, or auditing code quality.
open-mercato
testing-security
testing
1.2K
check-and-commit
Verify that the Open Mercato app is ready to publish by running build, generation, i18n, typecheck, unit test, and app build checks; fix obvious i18n sync or usage issues; and if everything passes, commit and push the current branch. Use this skill when the user asks to check the branch, make CI-style verification pass, fix i18n drift, then commit and push.
open-mercato
testing-security
testing
1.2K
integration-tests
Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Use when the user says "run integration tests", "test this feature", "create test for", "convert test case", "run QA tests", or "integration test".
open-mercato
testing-security
code-quality
1.2K
github-code-review
Review code changes by analyzing git diffs, leaving inline comments on PRs, and performing thorough pre-push review. Works with gh CLI or falls back to git + GitHub REST API via curl.
math-inc
testing-security
code-quality
1.2K
requesting-code-review
Use when completing tasks, implementing major features, or before merging. Validates work meets requirements through systematic review process.
math-inc
testing-security
testing
1.2K
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
math-inc
testing-security
security
1.2K
security-review
ๅจๆทปๅ ่บซไปฝ้ช่ฏใๅค็็จๆท่พๅ ฅใไฝฟ็จๆบๅฏไฟกๆฏใๅๅปบ API ็ซฏ็นๆๅฎ็ฐๆฏไป/ๆๆๅ่ฝๆถไฝฟ็จๆญคๆ่ฝใๆไพๅ จ้ข็ๅฎๅ จๆธ ๅๅๆจกๅผใ
cfrs2005
testing-security
testing
1.2K
tdd-workflow
ๅจ็ผๅๆฐๅ่ฝใไฟฎๅค Bug ๆ้ๆไปฃ็ ๆถไฝฟ็จๆญคๆ่ฝใๅผบๅถๆง่กๆต่ฏ้ฉฑๅจๅผๅ (TDD)๏ผๅ ๆฌๅๅ ๆต่ฏใ้ๆๆต่ฏๅ็ซฏๅฐ็ซฏ (E2E) ๆต่ฏ๏ผ็กฎไฟ่ฆ็็่พพๅฐ 80% ไปฅไธใ
cfrs2005
testing-security
code-quality
1.2K
snarkvm-review
Security-focused PR review for snarkVM codebase. WHEN: User says "review PR", "audit PR", "security review", "check PR changes", or wants thorough analysis of PR changes for bugs/vulnerabilities. WHEN NOT: Fixing review feedback (use snarkvm-fix pr), fetching context only (use snarkvm-github), or fixing issues (use snarkvm-fix).
ProvableHQ
testing-security
code-quality
1.2K
bug-hunter-stage1-input-randomization
bug-hunter ้ถๆฎต 1 ๆ่ฝใ่ด่ดฃๆๅไปฃ็ ๆนๅจใๆง่กๆๆไฟกๆฏ่ฑๆ๏ผๅนถๆๆไปถ/ไปฃ็ ๅ็ๆๅค่ฝฎ้ๆบๅ่พๅ ฅไปฅ็ผ่งฃ LLM ไฝ็ฝฎๅๅทฎใ
DragonOS-Community
testing-security
code-quality
1.1K
sdd-verify
Validate that implementation matches specs, design, and tasks. Trigger: When the orchestrator launches you to verify a completed (or partially completed) change.
Gentleman-Programming
testing-security
code-quality
1.1K
code-reviewer
Review code changes like a pragmatic senior engineer โ focus on functional bugs, regressions, type-safety, and missing tests. Use when performing code reviews on PRs or diffs in the rsdoctor repository.
web-infra-dev
testing-security
testing
1.1K
write-e2e-cases
Use when adding or updating Rsdoctor end-to-end tests in `e2e/cases/`, including new feature coverage, bug reproduction, and regression prevention.
web-infra-dev
testing-security
testing
1.1K
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
hotovo
testing-security
testing
1.1K
test-driven-development
Use when implementing complex logic that needs test coverage - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first; NOT for UI components, simple CRUD, or straightforward code
udecode
testing-security
code-quality
1.1K
golang-code-style
Golang code style, formatting and conventions. Use when writing code, reviewing style, configuring linters, writing comments, or establishing project standards.
samber
testing-security