code-quality
4.9K
verify-all-deliverables
Ensure all required output files are created and verified before marking a task complete
HKUDS
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
4.9K
verify-success-after-unknown-error
Verify task completion by checking filesystem state when execute_code_sandbox or run_shell return misleading unknown errors
HKUDS
testing-security
code-quality
4.9K
css-append-selector-verify
Safely append CSS styles from one file to another, with per-selector grep verification after every append to catch silent truncation that tail or wc-l alone would miss
HKUDS
testing-security
code-quality
4.9K
idempotent-file-replace
Read-then-diff before writing a file to ensure the write is skipped when the content already matches, preventing unnecessary modifications and downstream side effects.
HKUDS
testing-security
code-quality
4.9K
safe-css-append
Safely append CSS styles from one file to another by identifying missing rules, adapting CSS variables, and verifying changes
HKUDS
testing-security
code-quality
4.9K
typescript-typecheck-fallback
Reliably run TypeScript type-checking (npx tsc --noEmit) by using shell_agent as a fallback when run_shell fails due to environment or timeout issues.
HKUDS
testing-security
code-quality
4.9K
unicode-safe-file-writing
How to reliably write files containing multi-byte Unicode (emoji, special symbols) when write_file fails with 'unknown error' by falling back to run_shell with a heredoc.
HKUDS
testing-security
code-quality
4.9K
write-special-chars-readback
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.
HKUDS
testing-security
code-quality
4.9K
write-special-chars-ts-check
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.
HKUDS
testing-security
code-quality
4.9K
policy-check
This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
microsoft
testing-security
code-quality
4.9K
code-review-reception
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
microsoft
testing-security
testing
4.9K
ci-readiness-check
Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.
microsoft
testing-security
testing
4.9K
finishing-a-development-branch
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
microsoft
testing-security
testing
4.9K
test-driven-development-tdd
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
microsoft
testing-security
testing
4.9K
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
microsoft
testing-security
testing
4.8K
playwright-app-testing
Test the Expensify App using Playwright browser automation. Use when user requests browser testing, after making frontend changes, or when debugging UI issues
Expensify
testing-security
testing
4.8K
control-api-tests
Instructions for writing unit tests for new public APIs on WinForms controls and components. Covers test project structure, naming conventions, property tests, event tests, OnXxx method tests, SubControl patterns, data attributes, and handle-state verification.
dotnet
testing-security
testing
4.8K
gdi-rendering-tests
Instructions for writing unit tests for Graphics, Bitmap, GraphicsPath, and Font rendering APIs in System.Drawing. Covers bitmap-based verification, integer/float overload testing, version-guarded test blocks, and FluentAssertions patterns for path-point validation.
dotnet
testing-security
testing
4.8K
kotest
Helps write, migrate, and improve Kotlin tests using the Kotest testing framework. Covers test spec styles (FunSpec, DescribeSpec, BehaviorSpec, etc.), assertions (shouldBe, matchers, soft assertions), property-based testing (Arb, forAll, checkAll), data-driven testing, lifecycle hooks, extensions, coroutine testing, project configuration, and multiplatform setup. Use when the user mentions Kotest, kotest matchers, property testing with Arb, Kotest spec styles, shouldBe assertions, Kotlin test framework, or migrating from JUnit/TestNG/Spek to Kotest.
kotest
testing-security
code-quality
4.7K
code-review-expert
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
dtyq
testing-security
security
4.7K
skill-vetter
Security-first skill vetting protocol for AI agents. Use before installing any skill from the platform skill market, skillhub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns to determine whether a skill is safe to install.
dtyq
testing-security
code-quality
4.7K
pre-commit-checks
Use this skill when finalizing a bug fix or new feature before committing: after code changes are complete in lxd/, lxc/, shared/, or client/; before proposing a commit or pull request; or when asked to validate, lint, or check the build.
canonical
testing-security
testing
4.7K
clawteam-dev
Use this skill when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually works end-to-end. Use the repository bootstrap scripts to standardize the local `clawteam` command and to wire project-local `.agents` and `.claude` skills back to this repository. This skill is repository-development oriented, not a general end-user usage guide.
HKUDS
testing-security
code-quality
4.6K
docs-demo-local-test
Test the docs JSON repair demo against local backend changes before publishing. Use this when modifying docs/app.py or docs UI files and you need local end-to-end verification.
mangiucugna
testing-security