skills.rest
WesleyMFrederick
WesleyMFrederickCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

extract-package-to-repo

Extract a package from a monorepo into a standalone GitHub repository with history.

Updated Aug 23, 2026
Search Tags:#automation#repository#git-history#extract#issue-transfer#cc-workflows
One-click install
npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill extract-package-to-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract-package-to-repo
Source: https://github.com/WesleyMFrederick/cc-workflows-plugin/tree/main/src-claude/skills/extract-package-to-repo
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill extract-package-to-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts a package from a monorepo into its own standalone GitHub repository while preserving commit history, enabling a clean separation of ownership and tooling.

Core Features & Use Cases

  • Extract with full commit history from cc-workflows into a new repo.
  • Rename package identity and adjust npm/CLI bindings in the new repository.
  • Transfer GitHub issues and wire the original plugin as a .claude submodule for seamless integration.

Quick Start

Create the new repository, then configure the package path and target repo; run the Phase 1-7 workflow to complete the migration.

Frequently Asked Questions about extract-package-to-repo

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

FAQPage Schema
How do I extract a package from a monorepo into a standalone repository while preserving git history?▼

To extract a package from a monorepo while preserving git history, this Skill automates a multi-phase workflow using git-filter-repo to isolate the package directory, create a new standalone GitHub repository, and maintain full commit history.

What is the best way to migrate a package from cc-workflows to its own GitHub repo?▼

Migrating a package from cc-workflows to its own GitHub repo is handled by running a multi-phase workflow that extracts the package, renames its identity, transfers GitHub issues, and wires the original plugin as a .claude submodule.

Does extracting a package with git-filter-repo also transfer GitHub issues to the new repository?▼

Yes, extracting a package with git-filter-repo includes transferring GitHub issues to the new repository, ensuring a clean separation of ownership and tooling without losing historical issue tracking data.

Can I adjust npm and CLI bindings when moving a package out of a monorepo?▼

Yes, you can adjust npm and CLI bindings when moving a package out of a monorepo, as the extraction workflow includes renaming package identity and updating necessary configuration in the new repository.

What is a .claude submodule and how is it wired during repo extraction?▼

A .claude submodule is wired during repo extraction to maintain seamless integration with the original monorepo structure, allowing the newly extracted standalone repository to reference the original plugin setup.

What do I need to set up before running the package extraction workflow?▼

Before running the package extraction workflow, you need to create the new target GitHub repository, then configure the source package path and target repository details to execute the Phase 1-7 migration process.

Related Skills

Explore More Software Engineering Skills→
dwmkerrdwmkerr
23

project-setup

Create private GitHub repositories with branch protections, license, and README.

Community
Advanced
glhewettglhewett

git-submodule-commit

Commit and push git submodule changes and update the parent repository reference.

Community
Intermediate
erclxerclx
2

git-issue

Formats session context into GitHub issues and files them via GitHub CLI.

Community
Advanced
eduardo-sleduardo-sl
64

go-architecture-review

Review Go project architecture for package structure and dependency direction.

Community
Advanced