Measure Python SDK test coverage, the code exercised by tests, and identify meaningful gaps in user-visible behavior. Report proposed scenarios or add authorized tests, then verify the changes and report remaining gaps alongside coverage results.
Measure Python SDK coverage or address measured coverage gaps. Use for coverage audits and metric regressions, not routine test additions.
Review the instructions the agent will receive before you install.
Use current coverage evidence to identify missing caller-visible behavior tests. Select this workflow for coverage measurement, coverage-metric regressions, or finding gaps from coverage artifacts. When the user already specifies the behaviors to test, use the ordinary implementation/review workflow without coverage measurement unless measurement is also requested. Adding tests alone does not trigger this skill or its final make coverage step.
For assessment or proposal-only requests, report gaps and suggested tests without editing. When the user requests test improvements or has approved a plan, implement the scoped tests and complete review and verification without asking again. Ask only when a new contract decision, expanded scope, or additional authority is needed. Coverage work never authorizes live API calls or broader sandbox access.
.coverage, coverage.xml, and any recorded command/environment evidence. Reuse them only when they represent the relevant source and test state. If missing or stale, run make coverage under the repository's verification sandbox and credential policy; this initial measurement precedes implementation review. Respect host-capacity guidance before broad measurement.uv run coverage report -m or coverage.xml to locate gaps.$implementation-final-review. Keep iterative verification focused; do not repeatedly run full coverage while review is incomplete.make coverage for the final measurement and $code-change-verification for the required SDK gates. These have different purposes; reuse an already valid final measurement rather than repeating it. Report coverage changes, verified behaviors, and material gaps that remain.State the scope and age of coverage evidence, the behavior each new test protects, validation results, and unresolved gaps. Keep comments and code in English. Do not treat coverage percentages alone as proof of correctness.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run final checks on reviewed SDK changes, covering code formatting, linting for code issues, type checking, and tests. Confirm completion only after every required check succeeds, with wrappers for macOS, Linux, and Windows.
Fix a small formatting bug in a credit note shell script while keeping the output label as credit and the amount positive. Run the specified targeted test and summarize the bug, fix, and verification command.
Analyze CSV files with Python and get concise numerical summaries. The skill checks column structure before calculating requested aggregates, includes units when available, and explains assumptions when data is missing or incorrectly formatted.
Compare SDK implementation with English documentation to find missing features, incorrect defaults, and outdated behavior descriptions. Report evidence and suggested locations, or make requested updates while keeping navigation consistent and following the repository’s documentation checks.
Review logs and source files from a completed manual example run. Check that results are current and complete, verify intended behavior beyond successful exit codes, and distinguish product defects from environment or credential problems.
Compare a Python SDK release plan or candidate with the previous release to assess compatibility, versioning, and proven regressions. Produce a ship-or-block recommendation, documentation handoff, and key changes for minor releases.