pokeswift-tuist-refactor-guard

Plan and validate Swift refactors within the Tuist workspace and target graph.

365|38|Updated Mar 9, 2026

Search Tags:#code quality #refactoring #swift #build system #tuist #poke-swift

Ready to run

npx skills add https://github.com/Dimillian/PokeSwift --skill pokeswift-tuist-refactor-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pokeswift-tuist-refactor-guard
Source: https://github.com/Dimillian/PokeSwift/tree/main/.agents/skills/pokeswift-tuist-refactor-guard
Command: npx skills add https://github.com/Dimillian/PokeSwift --skill pokeswift-tuist-refactor-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents breaking the PokeSwift project's build system and module integrity during code refactoring, ensuring stability and maintainability.

Core Features & Use Cases

Refactor Planning: Helps map out code changes and identify ownership boundaries.
Build System Validation: Ensures the Tuist workspace and target graph remain intact after modifications.
Use Case: Before moving a large file from PokeCore to PokeUI, use this Skill to plan the move, verify dependencies, and confirm that tuist generate runs without errors, preventing build failures.

Quick Start

Use the pokeswift-tuist-refactor-guard skill to plan a refactor of the PokeCore module.

Frequently Asked Questions about pokeswift-tuist-refactor-guard

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

FAQPage Schema

How do I safely refactor Swift files without breaking the Tuist workspace?▼

To safely refactor Swift files within a Tuist workspace, you must map out structural changes, verify module ownership boundaries, and confirm the target graph remains intact before executing modifications.

What is the best way to move a file between modules in a Swift project using Tuist?▼

Moving a file between Swift modules using Tuist requires planning the directory transfer, checking dependency ownership, and running `tuist generate` to validate that the build system accepts the new structure.

Does refactoring PokeSwift modules require validating the Xcodebuild target graph?▼

Refactoring PokeSwift modules requires Xcodebuild target graph validation to ensure structural changes maintain stable public APIs and do not disrupt the existing build architecture.

Can I use automated validation to prevent build failures when changing Swift directory structures?▼

Automated validation can prevent build failures during Swift directory changes by applying layered checks through Tuist and Xcodebuild to verify module dependencies and workspace integrity.

Why does tuist generate fail after moving files between PokeCore and PokeUI?▼

Tuist generate fails after moving files between PokeCore and PokeUI because the target graph and module ownership boundaries are disrupted, requiring dependency verification and structural validation before generation.