Testing & Security skills

Check whether a README actually lets a stranger run the project. Use on any repo's README before publishing.

The English summary is being prepared. Showing the original description.

Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.

The English summary is being prepared. Showing the original description.

Diagnose and fix tests that pass sometimes and fail other times. Use when CI is red intermittently.

The English summary is being prepared. Showing the original description.

Find the untested code paths that actually matter, not just the coverage percentage. Use after adding tests.

The English summary is being prepared. Showing the original description.

Test the boundary between two systems by the contract, not the implementation. Use for APIs, integrations, and shared interfaces.

The English summary is being prepared. Showing the original description.

Security-review a diff against the OWASP Top 10. Use before merging anything that touches auth, input handling, queries, or external calls.

The English summary is being prepared. Showing the original description.

Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.

The English summary is being prepared. Showing the original description.

Audit Maven dependencies for outdated versions, security vulnerabilities, and conflicts. Use when user says "check dependencies", "audit dependencies", "outdated deps", or before releases.

The English summary is being prepared. Showing the original description.

Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.

The English summary is being prepared. Showing the original description.

Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.

The English summary is being prepared. Showing the original description.

Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.

The English summary is being prepared. Showing the original description.

Write the test first, watch it fail, write minimal code to pass

The English summary is being prepared. Showing the original description.

TDD for process documentation - test with subagents before writing, iterate until bulletproof

The English summary is being prepared. Showing the original description.

RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes

The English summary is being prepared. Showing the original description.

Replace arbitrary timeouts with condition polling for reliable async tests

The English summary is being prepared. Showing the original description.

Use for authorized security assessment of LLM applications and AI agents, including prompt injection, tool abuse, RAG exposure, memory poisoning, and model supply-chain risks.

The English summary is being prepared. Showing the original description.

Use for authorized database security assessment covering PostgreSQL/MySQL/MSSQL/Mongo/Redis exposure, authz, UDF/command paths, and misconfiguration review.

The English summary is being prepared. Showing the original description.

Use for authorized email security review including phishing analysis, header authentication (SPF/DKIM/DMARC), BEC patterns, and mailbox token abuse research.

The English summary is being prepared. Showing the original description.

Use for authorized OT/ICS security assessment covering Purdue model zoning, PLC/SCADA exposure, industrial protocol discovery, and safe passive-first evaluation.

The English summary is being prepared. Showing the original description.

Use for authorized source-code security review and SAST workflows including Semgrep, CodeQL patterns, dangerous API hunting, and fix verification.

The English summary is being prepared. Showing the original description.

Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.

The English summary is being prepared. Showing the original description.

Use for authorized hardware and embedded interface security research including UART/JTAG discovery, debug pad triage, secure boot overview, and offline firmware extraction support.

The English summary is being prepared. Showing the original description.

主动渗透测试工具链。覆盖信息收集、端口扫描、漏洞扫描、Web 渗透、SQL 注入、目录爆破、密码破解等场景。 通过 MCP server（pentestMCP / mcp-security-hub）将 20+ 安全工具暴露给 AI agent。 触发关键词：渗透测试、端口扫描、Nmap、漏洞扫描、Nuclei、SQL 注入、SQLMap、目录爆破、FFUF、密码破解、Hashcat、信息收集、子域名、Web 渗透、ZAP、Burp。

The English summary is being prepared. Showing the original description.

Use for authorized macOS and Mach-O reverse engineering including codesign, Objective-C/Swift recovery, endpoint security surfaces, and Apple platform malware analysis.

The English summary is being prepared. Showing the original description.