objc-test-gap-mapper

Identify Objective-C source modules lacking corresponding test files by comparing basenames and directory structures.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/jvalinsky/garazyk --skill objc-test-gap-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: objc-test-gap-mapper
Source: https://github.com/jvalinsky/garazyk/tree/main/skills/objc-test-gap-mapper
Command: npx skills add https://github.com/jvalinsky/garazyk --skill objc-test-gap-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify Objective-C source files that may lack corresponding test coverage, enabling focused efforts on improving code reliability.

Core Features & Use Cases

  • Test Gap Identification: Analyzes source and test directories to map implementation files to potential test files.
  • Risk Prioritization: Ranks uncovered source files based on module criticality and potential risk.
  • Use Case: Before a major refactor, use this Skill to quickly understand which parts of the codebase have the weakest test safety net, allowing you to prioritize where to add new tests.

Quick Start

Run the map_test_gaps.sh script from the repository root, specifying an output directory.

Frequently Asked Questions about objc-test-gap-mapper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find Objective-C source files lacking test coverage?

This Skill identifies Objective-C source files lacking test coverage by comparing file basenames and directory structures between your source and test folders to map implementation files to potential test files.

How do I prioritize which Objective-C modules need tests before refactoring?

Prioritize uncovered Objective-C modules for refactoring by using gap analysis to rank source files based on module criticality and potential risk factors, highlighting the weakest test safety nets.

Do I need shell scripting to map Objective-C tests to source code?

Yes, mapping Objective-C tests to source code requires shell scripting to enumerate and compare file system entries within specified source and test directories from your repository root.

What is Objective-C test gap analysis and how does it work?

Objective-C test gap analysis is a process that identifies source modules without test files by comparing directory structures and file basenames, then prioritizes uncovered sources based on criticality and risk.

Can I use this test gap mapper for large Objective-C codebases?

Yes, you can use this test gap mapper for large Objective-C codebases by running the shell script from the repository root and specifying an output directory to capture the uncovered source file mappings.