test-sync

Analyze and synchronize test files with source code to detect orphaned, missing, and implementation-coupled tests.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill test-sync-robit-man
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-sync
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/test-sync
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill test-sync-robit-man

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires re, glob, os, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures your test suite accurately reflects your codebase, preventing wasted effort on outdated tests and identifying gaps in test coverage.

Core Features & Use Cases

  • Orphaned Test Detection: Identifies tests for code that has been deleted or renamed.
  • Missing Test Detection: Finds source files that lack corresponding tests.
  • Implementation-Coupled Test Detection: Flags tests that rely on internal implementation details, making them brittle.
  • Use Case: After a major refactoring, use this Skill to automatically find and report any tests that are no longer relevant or that need to be updated to reflect the new code structure.

Quick Start

Run the test sync skill to find orphaned tests and missing tests in the current project.

Frequently Asked Questions about test-sync

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

FAQPage Schema
How do I find orphaned tests after a major code refactoring?

Detect orphaned tests after refactoring by analyzing test files against source code using AST analysis and pattern matching, identifying tests that reference deleted or renamed code to ensure test-code alignment.

What is implementation-coupled test detection and why does it matter?

Implementation-coupled test detection identifies tests relying on internal implementation details rather than public behavior, flagging brittle tests likely to break during refactoring and increasing test maintenance overhead.

How do I check for missing test coverage in my source files?

Check for missing tests by globbing source files and applying AST analysis to find source code modules lacking corresponding test files, validating traceability and coverage gaps across your software project.

Does test synchronization work with Python scripts for file pattern matching?

Yes, test synchronization uses Python scripts for file globbing, AST analysis, and pattern matching to ensure test-code alignment, requiring the standard libraries re, glob, and os to run.

When should I run a test suite cleanup to remove outdated tests?

Run a test suite cleanup when you need traceability validation after significant code changes, ensuring you are not wasting effort on outdated tests and identifying gaps in test coverage.

What's the best way to maintain test-code traceability in software projects?

Maintain test-code traceability by automating test synchronization using AST analysis and pattern matching to continuously detect orphaned, missing, and implementation-coupled tests across software projects.