一键导入
find-missing-tests
Analyze codebase and identify missing test cases, then create GitHub issues for each gap
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze codebase and identify missing test cases, then create GitHub issues for each gap
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Argus — all-in-one information gathering & reconnaissance toolkit. 135 modules covering network infrastructure, web app analysis, and security/threat intelligence. Use for domain recon, subdomain enum, SSL analysis, tech stack detection, vulnerability scanning, and OSINT.
Manage secrets via Bitwarden CLI (bw). Use when pulling secrets into a shell session, creating/updating Secure Notes from .env files, listing vault items, or setting up Bitwarden on a new machine. Secrets live in Bitwarden, get loaded into memory on demand, and die with the shell session — no files on disk.
Develop a thorough, step-by-step specification for a given idea
Set up a recurring build tracker cron job for any GitHub repo. Runs a zero-LLM shell script to detect stale PRs, stale assigned issues, and phase progress, then posts to a Discord channel only when there's something actionable. Use when asked to "track this build every N hours", "prod agents on a project", "set up a build monitor", "watch this repo for stale work", or similar. The tracker is cheap to run — script does all the work, the agent only speaks when findings exist.
Run long-running coding tasks in cloud environments (Claude Code or Codex), with session teleporting and automatic PR creation.
Delegate coding tasks to subagents or run Claude Code/Codex in tmux sessions. Use the Task tool for focused multi-step coding work. Use tmux for long-running interactive sessions, parallel worktree-based fixes, and PR reviews. NOT for simple single-file edits — do those directly.
| name | find-missing-tests |
| description | Analyze codebase and identify missing test cases, then create GitHub issues for each gap |
| user-invocable | true |
Analyze codebase and identify missing test cases, then create GitHub issues for each gap: $ARGUMENTS
Follow these steps:
Analyze the codebase:
Review existing test structure:
Identify specific missing test cases:
Create detailed GitHub issues for each missing test with:
[TEST] Add {type} tests for {component/function}Generate GitHub issues:
gh issue create for each identified test gaptesting, bug, enhancementCreate a summary report:
test-coverage-analysis.mdRemember: Be specific about what should be tested - don't create vague "add more tests" issues.