aiskillstore/marketplace / skills/5t111111/testing
testing
VerifiedGuide for testing practices and frameworks
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 737 B |
| skill-report.json | config | 9.2 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-04T17:03:04.791Z",
"slug": "5t111111-testing",
"source_url": "https://github.com/5t111111/tailwind-theme-figma-variables/tree/main/.github/skills/testing",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "fcf97871fd7af90917ddef049867ca59b7cb754121abed96e4aa398caf2b926b",
"tree_hash": "507e4592da3ea24e0a310ad48b334f42c126af62f50cb7f20a3aceda49259906",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "testing",
"description": "Guide teams in writing, organizing, and running Deno tests with consistent coverage expectations.",
"summary": "Testing guidance for Deno projects using colocated test files and clear coverage standards.",
"icon": "📦",
"version": "1.0.1",
"author": "5t111111",
"license": "MIT",
"category": "coding",
"tags": [
"testing",
"deno",
"test-coverage",
"quality-assurance",
"developer-workflow"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "The two static findings are Markdown inline code spans, not Ruby or shell backtick execution. The skill is prompt-only testing guidance with no evidence of prompt injection, data exfiltration, or malicious intent.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 16,
"line_end": 16
},
{
"file": "SKILL.md",
"line_start": 24,
"line_end": 24
}
]
}
],
"static_findings": [
{
"id": "external_commands:SKILL.md:16:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 16,
"line_end": 16,
"snippet": "- Write tests in separate files with the `.test.ts` extension in the same"
},
{
"id": "external_commands:SKILL.md:24:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 24,
"line_end": 24,
"snippet": "- Use the command `mise run test` to run all tests in the project"
}
],
"finding_verdicts": [
{
"id": "external_commands:SKILL.md:16:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "Line 16 uses Markdown inline code for the `.test.ts` filename extension. It does not execute Ruby, shell commands, or user-controlled input."
},
{
"id": "external_commands:SKILL.md:24:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "Line 24 documents a fixed project test command in Markdown. It is normal testing guidance, not executable code in the skill itself."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 1,
"total_lines": 26,
"audit_model": "codex",
"audited_at": "2026-07-04T17:03:04.791Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Improve Deno Testing Practices",
"value_statement": "Teams need consistent test structure and clear coverage expectations. This skill guides Deno test writing, file placement, edge case coverage, and test execution.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"Deno testing",
"TypeScript tests",
"test coverage",
"edge case testing",
"mise run test",
"developer workflow",
"AI testing guidance"
],
"actual_capabilities": [
"Recommends the built-in Deno testing framework for tests.",
"Defines the `.test.ts` file naming convention for test files.",
"Advises placing tests beside the code they cover.",
"Requires tests for public functions and methods.",
"Encourages descriptive test names, edge cases, and error handling.",
"Specifies `mise run test` as the project test command."
],
"limitations": [
"Does not provide full test templates or assertion examples.",
"Does not explain mocking, fixtures, or integration test setup.",
"Assumes the project uses Deno and has a `mise run test` task.",
"Does not cover CI configuration or coverage reporting."
],
"use_cases": [
{
"title": "Deno Feature Testing",
"description": "Plan tests for a new Deno feature with file placement, public API coverage, edge cases, and error handling.",
"target_user": "TypeScript developer"
},
{
"title": "Pull Request Review",
"description": "Check whether a change includes clear tests before it is approved or merged.",
"target_user": "Code reviewer"
},
{
"title": "Team Test Standards",
"description": "Define simple testing expectations for contributors working in the same Deno codebase.",
"target_user": "Engineering lead"
}
],
"prompt_templates": [
{
"title": "Create Basic Tests",
"prompt": "Help me add Deno tests for this module. Use `.test.ts` files beside the source and include descriptive test names.",
"scenario": "Beginner test creation"
},
{
"title": "Review Test Coverage",
"prompt": "Review my test plan for [feature]. Check whether public functions, edge cases, and error handling are covered.",
"scenario": "Intermediate coverage review"
},
{
"title": "Build a Test Checklist",
"prompt": "Design a testing checklist for this Deno project. Include file placement, naming, edge cases, error handling, and the `mise run test` step.",
"scenario": "Advanced project workflow"
},
{
"title": "Audit a Pull Request",
"prompt": "Audit this pull request for testing gaps. Identify missing public function tests, weak case names, uncovered edge cases, and verification steps.",
"scenario": "Advanced review support"
}
],
"output_examples": [
{
"input": "Add tests for a new date parser.",
"output": "Place a date parser test file beside the module. Cover valid dates, invalid formats, timezone boundaries, and parser errors."
},
{
"input": "Prepare a pull request for review.",
"output": [
"Confirm each public function has a matching test.",
"Check that test names describe expected behavior.",
"Run the project test command before submission."
]
},
{
"input": "Improve an existing test suite.",
"output": "Look for missing edge cases, weak error handling coverage, and unclear test names. Prioritize public APIs first."
}
],
"best_practices": [
"Create test files beside the source files they cover.",
"Write clear test names that explain the behavior under review.",
"Cover public APIs, edge cases, and error handling before committing."
],
"anti_patterns": [
"Leaving public functions without corresponding tests.",
"Using vague test names that hide the expected behavior.",
"Submitting changes before running the project test suite."
],
"faq": [
{
"question": "What kind of projects does this skill support?",
"answer": "It supports Deno and TypeScript projects that use colocated test files and a project test command."
},
{
"question": "Does this skill write complete test files?",
"answer": "It gives testing guidance and structure. Users must provide project code and exact behavior for complete tests."
},
{
"question": "Can I use it with Claude, Codex, or Claude Code?",
"answer": "Yes. The skill is compatible with Claude, Codex, and Claude Code workflows."
},
{
"question": "Does it require external services?",
"answer": "No. The skill is prompt-only and does not require network access or external services."
},
{
"question": "What test command does it recommend?",
"answer": "It recommends using the project's `mise run test` command to run all tests."
},
{
"question": "What testing gaps does it emphasize?",
"answer": "It emphasizes public API coverage, descriptive names, edge cases, and error handling."
}
]
},
"file_structure": [
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 26
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |