원클릭으로 Manus에서 모든 스킬 실행

시작하기

find-missing-tests

스타0

포크0

업데이트2026년 4월 10일 10:44

Analyze codebase and identify missing test cases, then create GitHub issues for each gap

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

stevengonsalvez

stevengonsalvez/nanoclaw-standalone

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 품질 보증 분석가·테스터컴퓨터 및 수학직·SOC 15-1253

SKILL.md

readonly

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:
- If $ARGUMENTS specifies files/directories, focus on those areas
- Otherwise, scan the entire codebase for test coverage gaps
- Look for functions, classes, and modules without corresponding tests
- Identify edge cases and error conditions that aren't tested
Review existing test structure:
- Understand the current testing framework and patterns
- Identify test file naming conventions
- Note any existing test utilities or helpers
- Check for integration and end-to-end test coverage
Identify specific missing test cases:
- Unit tests: Functions and methods without test coverage
- Integration tests: Component interactions not tested
- Edge cases: Boundary conditions, error handling, null/empty inputs
- Regression tests: Previously fixed bugs without test coverage
- Performance tests: Critical paths without performance validation
Create detailed GitHub issues for each missing test with:
- Clear title: [TEST] Add {type} tests for {component/function}
- Specific test cases to implement
- Expected test file location following project conventions
- Acceptance criteria defining what constitutes complete coverage
- Priority level based on code criticality
Generate GitHub issues:
- Use gh issue create for each identified test gap
- Add appropriate labels: testing, bug, enhancement
- Include code snippets showing what needs testing
- Reference related code files and line numbers
Create a summary report:
- Save findings as test-coverage-analysis.md
- Include overall coverage assessment
- Prioritize issues by criticality and risk

Remember: Be specific about what should be tested - don't create vague "add more tests" issues.

이 저장소의 다른 Skills

같은 저장소

argus

stevengonsalvez/nanoclaw-standalone

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.

2026-04-100

bitwarden

stevengonsalvez/nanoclaw-standalone

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.

2026-04-100

brainstorm

stevengonsalvez/nanoclaw-standalone

Develop a thorough, step-by-step specification for a given idea

2026-04-100

build-tracker

stevengonsalvez/nanoclaw-standalone

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.

2026-04-100

cloud-coding-agent

stevengonsalvez/nanoclaw-standalone

Run long-running coding tasks in cloud environments (Claude Code or Codex), with session teleporting and automatic PR creation.

2026-04-100

coding-agent

stevengonsalvez/nanoclaw-standalone

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.

2026-04-100

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:
- If $ARGUMENTS specifies files/directories, focus on those areas
- Otherwise, scan the entire codebase for test coverage gaps
- Look for functions, classes, and modules without corresponding tests
- Identify edge cases and error conditions that aren't tested
Review existing test structure:
- Understand the current testing framework and patterns
- Identify test file naming conventions
- Note any existing test utilities or helpers
- Check for integration and end-to-end test coverage
Identify specific missing test cases:
- Unit tests: Functions and methods without test coverage
- Integration tests: Component interactions not tested
- Edge cases: Boundary conditions, error handling, null/empty inputs
- Regression tests: Previously fixed bugs without test coverage
- Performance tests: Critical paths without performance validation
Create detailed GitHub issues for each missing test with:
- Clear title: [TEST] Add {type} tests for {component/function}
- Specific test cases to implement
- Expected test file location following project conventions
- Acceptance criteria defining what constitutes complete coverage
- Priority level based on code criticality
Generate GitHub issues:
- Use gh issue create for each identified test gap
- Add appropriate labels: testing, bug, enhancement
- Include code snippets showing what needs testing
- Reference related code files and line numbers
Create a summary report:
- Save findings as test-coverage-analysis.md
- Include overall coverage assessment
- Prioritize issues by criticality and risk

Remember: Be specific about what should be tested - don't create vague "add more tests" issues.