track-files

Discover and track file batches using glob patterns and grep across a codebase.

1|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill track-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-files
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/track-files
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill track-files

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage and track large batches of files that require similar modifications, preventing errors and ensuring consistency during complex refactoring or migration tasks.

Core Features & Use Cases

  • Codebase-wide Search: Automatically discovers files based on patterns or content across monorepos.
  • Context Gathering: Collects per-file context like imports and exports to aid downstream operations.
  • Progress Tracking: Creates manifests with checkboxes to monitor the status of file modifications.
  • Use Case: When refactoring a core component used in over 50 places, use this Skill to find all instances, document their dependencies, and create a trackable list for the refactoring process.

Quick Start

Use the track-files skill to find all files matching the pattern *.helper.ts and prepare them for renaming.

Frequently Asked Questions about track-files

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

FAQPage Schema
How do I track files across a monorepo during large-scale code refactoring?

To track files for code refactoring across a monorepo, use glob patterns and grep to discover matching batches, gather contextual imports and exports, and generate a persistent manifest for progress tracking.

What is the best way to manage batch operations on a large codebase without missing files?

Managing batch operations on a large codebase requires generating a persistent manifest with checkboxes to document file modifications, ensuring comprehensive coverage and preventing errors during complex migrations.

How do I prepare a large batch of files for similar code modifications?

You prepare files for similar code modifications by searching the codebase based on patterns or content, collecting per-file context like imports and exports, and creating a trackable list to monitor the modification status.

Does batch file tracking work for component migrations used in many different places?

Yes, batch file tracking works for component migrations by finding all component instances, documenting their dependencies, and creating a trackable list to ensure consistent refactoring across the codebase.

What context is gathered for each file when documenting codebase changes?

When documenting codebase changes, the context gathered for each file includes its imports and exports, which provides necessary dependency information to aid downstream batch operation workflows.

Why do I need a manifest for monorepo batch operations and codebase migrations?

You need a manifest for monorepo batch operations to systematically monitor the status of file modifications, ensuring comprehensive coverage and preventing consistency errors during complex refactoring tasks.