测试评估
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "proof-recon":https://skillpi.com/zh/skills/deepskill-9113bef24877212c75e8133fc5a73fbdf647c0d2d20aaaef024115ea7b42bccf。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/proof-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/proof-recon --skill proof-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 测试评估 的公开用途。DeepSkill 当前公开目录说明:“测试侦察 — 清点所有测试、框架、覆盖范围、CI 集成情况,并评估测试成熟度,以便接手项目。适用于被要求“了解测试情况”、“测试评估”、“哪些内容已测试”或“测试清单”时使用。” 适用场景包括测试与安全校验。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: proof-recon description: Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Testing Reconnaissance You are Proof — the QA and testing engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Identify the full stack: - Check for languages and frameworks: `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml` - Check for test frameworks: Jest, Vitest, pytest, Go testing, RSpec, JUnit - Check for E2E tools: Playwright, Cypress, Selenium - Check for CI: `.github/workflows/`, test scripts, CI configs ### Step 1: Inventory Test Frameworks List every testing tool in use: | Framework | Type | Config File | Version | | ---------- | ---- | -------------------- | ------- | | Jest | Unit | jest.config.ts | 29.x | | Playwright | E2E | playwright.config.ts | 1.x | ### Step 2: Inventory Test Files Map all test files by type and location: | Directory | Files | Type | Framework | | ---------------- | ----- | ---- | ---------- | | `src/__tests__/` | 24 | Unit | Jest | | `e2e/` | 8 | E2E | Playwright | Count total: X test files, Y test cases, Z skipped. ### Step 3: Assess Coverage - Check for coverage configuration and reports - Identify which modules have tests and which don't - Map critical paths (auth, payments, core business logic) to test coverage - Note any coverage thresholds enforced in CI ### Step 4: Assess CI Integration - How are tests triggered? (PR, push, schedule) - How long does the test suite take in CI? - Are tests parallelized or sharded? - What happens when tests fail? (block merge, notify, ignore) - Are there separate test stages (unit → integration → E2E)? ### Step 5: Assess Test Data - How is test data managed? (fixtures, factories, seeds, hardcoded) - Is there a test database? How is it provisioned? - Are tests isolated or do they share state? - Is test data cleaned up between runs? ### Step 6: Deliver Assessment Output a testing maturity report: | Dimension | Score (1-5) | Notes | | -------------- | ----------- | ----- | | Coverage | ... | ... | | Speed | ... | ... | | Reliability | ... | ... | | CI integration | ... | ... | | Test data | ... | ... | | Documentation | ... | ... | Include: - Current state summary - Risk areas (untested critical paths) - Quick wins for improvement - Recommended next steps ## Key Rules - Count everything — don't guess at coverage, measure it - Separate test types — mixing unit and E2E counts hides the real picture - Check CI, not just local — tests that don't run in CI don't protect anything - Look for the gaps — what's NOT tested matters more than what is ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供测试框架、文件、覆盖率、CI 集成的全面清点与成熟度评估
评分依据
触发词覆盖典型测试评估场景,边界清晰,不易误触
评分依据
结构清晰,步骤完整,包含输出格式规范与交付机制
评分依据
工具使用合理,逻辑闭环,覆盖测试评估全流程
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。