source-command-gf-refactor-plan

Generate a Graphify-based refactor plan for a specified module path.

3|Updated May 11, 2026
One-click install
npx skills add https://github.com/JeromyJSmith/lattice-platform --skill source-command-gf-refactor-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-gf-refactor-plan
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/source-command-gf-refactor-plan
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill source-command-gf-refactor-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you refactor a code module that uses the migrated gf-refactor-plan source command by turning the target into an actionable Graphify-based plan instead of relying on guesswork.

Core Features & Use Cases

  • Module-scoped planning: Generate a refactor plan for a specific path by setting the MODULE environment variable (defaulting to pixeltable/).
  • Operational output to stdout: Prints the resulting plan directly to standard output for easy review and copy/paste into other workflows.
  • Use Case: When you need to systematically restructure the Pixeltable ingestion boundary, you can request a plan for pixeltable/ to align changes with the Graphify migration approach.

Quick Start

Run the gf-refactor-plan skill with MODULE set to pixeltable/ so it prints the Graphify refactor plan for that module to stdout.

Frequently Asked Questions about source-command-gf-refactor-plan

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

FAQPage Schema
How do I generate a Graphify refactor plan for a specific module?

To generate a Graphify refactor plan, you target a specific directory by setting the MODULE environment variable. The skill defaults to the pixeltable/ directory and outputs the actionable migration plan directly to stdout.

What is a Graphify-based refactor plan used for in code migration?

A Graphify-based refactor plan is used to systematically restructure code modules during migration. It replaces guesswork by turning a target directory like the pixeltable ingestion boundary into an actionable plan printed to stdout.

Can I target a custom directory path instead of the default pixeltable module?

Yes, you can target a custom directory path by setting the MODULE environment variable before running the source command. If MODULE is not specified, the refactor plan generation defaults to the pixeltable/ directory.

How does the gf-refactor-plan source command output its migration plan?

The source command outputs its refactor plan directly to standard output (stdout). Printing the Graphify plan to stdout allows you to easily review the results and copy or paste them into other repository workflows.

What is the best way to plan changes for the pixeltable ingestion boundary?

The best way to plan changes for the pixeltable ingestion boundary is to generate a module-scoped Graphify refactor plan. By defaulting the MODULE variable to pixeltable/, it provides a systematic restructuring plan aligned with the migration approach.