Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks…
End-to-end verification of a change to keploy/keploy using keploy's own record/replay against a real sample application. Use whenever the user asks to test a change, verify a fix, prove that a modification works in practice, add e2e coverage for a PR, reproduce a bug against a sample app, or wire a behavior into CI.…
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.
Automatically generate comprehensive test cases from API definitions, endpoint descriptions, OpenAPI/Swagger specs, Postman collections, or raw HTTP request/response examples. Use this skill whenever the user mentions generating tests from APIs, writing test cases for REST endpoints, API testing, creating test suites…
Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing. Use this skill whenever the user wants to run Newman in a CI pipeline, integrate Postman collections into automated builds, set up API tests in GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, or…
Fast, template-based vulnerability scanning using ProjectDiscovery's Nuclei with extensive community templates covering CVEs, OWASP Top 10, misconfigurations, and security issues across web applications, APIs, and infrastructure. Use when: (1) Performing rapid vulnerability scanning with automated CVE detection, (2)…
A project-specific guide for adding and maintaining API tests with pytest in a test-automation codebase. API tests send requests to application endpoints and check their responses.
API testing patterns for Playwright -- apiRequest fixture usage, Zod response schema creation and validation, test.step wrapping for multi-call tests, per-field negative/validation testing, path parameter fuzzing, and helper fixtures for shared setup/teardown. Use when writing or updating API test specs, adding tests…
Reviews a Git branch as a pull request against the base branch (auto-resolved from origin/HEAD — usually main or master) using this repo's own rules — the CLAUDE.md constitution and the .claude/skills/ that apply to the changed files. Fetches the branch, switches to it, diffs it against the merge-base, routes the…
A guide for moving API definitions between Apifox and formats such as OpenAPI and Postman. OpenAPI is a standard format for describing an API, while Postman is a tool for working with APIs.
A guide for managing Apifox interface test cases and test data. A test case defines checks for one API, and test data supplies the values used during those checks.
Generate, modify, validate, execute and triage Flow Forge API test cases. Use when the user wants to turn requirement documents, API documents, table structures or business rules into executable YAML/Excel test cases, revise existing cases after requirement/API changes, run cases with the Flow Forge executor and…
Reviews shell scripts (.sh) for security, portability, and robustness anti-patterns. Provides structured fixes citing reference documentation. Use when reviewing bash/shell scripts or when asking to check shell script quality. Do not use for Python/Ruby/Go scripts, GitHub Actions YAML, or issues already caught by…
Analyzes, fixes, improves, and secures GitHub Actions workflows. Use when auditing CI/CD security, diagnosing broken workflows, making surgical changes, or optimizing performance. Do not use for non-GitHub-Actions CI systems (Jenkins, GitLab CI).
Turn a test failure into a structured bug report with repro steps, severity, and expected vs actual. Use when the user runs /bug-from-failure or asks to file a bug from a failing test.
Generate a Playwright API test file covering success, errors, auth failure, and invalid input. Use when the user runs /new-api-spec or asks for tests for an API endpoint.
Bootstrap the Autoframe framework for a specific product: asks about the app, then wires a ready-to-run Playwright suite. Use when the user runs /setup, asks to set up or initialize Autoframe, or wants to start a test suite for their app.