intent-migrate

Migrate local .sejas intents to the global ~/.claude-intents folder.

2|1|Updated Jan 12, 2026

Search Tags:#git #workflow #migration #claude #organization #intents

Ready to run

npx skills add https://github.com/sejas/ai-code-skills --skill intent-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intent-migrate
Source: https://github.com/sejas/ai-code-skills/tree/main/plugins/intents/commands/intent-migrate
Command: npx skills add https://github.com/sejas/ai-code-skills --skill intent-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users transition their locally stored intents to a centralized global storage location, ensuring better organization and accessibility across projects.

Core Features & Use Cases

Local to Global Migration: Moves intents from .sejas/ to ~/.claude-intents/.
Name Transformation: Renames intents to include the repository name for uniqueness.
Use Case: After deciding to centralize all your project intents, you can use this skill to consolidate intents scattered in various project-specific .sejas folders into one organized global directory.

Quick Start

Run the intent-migrate skill to move your local intents to the global folder.

Frequently Asked Questions about intent-migrate

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

FAQPage Schema

How do I migrate local intents to a centralized global storage folder?▼

To migrate local intents to a centralized global storage folder, run the migration script to move files from the local .sejas directory to the global ~/.claude-intents folder, organizing them into 'in-progress' and 'done' subdirectories.

How does the intent migration process handle naming conflicts across different repositories?▼

The intent migration process handles naming conflicts by prepending the repository name to the intent description, ensuring each migrated intent remains uniquely identifiable when consolidated in the global ~/.claude-intents directory.

Can I automatically clean up the old .sejas directory after moving my project intents?▼

Yes, you can clean up the old .sejas directory after moving your project intents, because the migration script offers an optional cleanup step to remove the local directory once the global consolidation is successfully completed.

What is the best way to organize scattered project intents into one accessible location?▼

The best way to organize scattered project intents is to centralize them by migrating local .sejas folders into a single global ~/.claude-intents directory, which categorizes the intents into 'in-progress' and 'done' subdirectories.

Do I need a specific workflow structure to consolidate local intents into global storage?▼

You need an existing local .sejas directory containing your saved intents to consolidate them into global storage, as the migration script reads from this specific folder structure and transfers the files to ~/.claude-intents.