new-forever-claude-clone

Automating private GitHub repository creation from a template requires cloning the source repo with full history, initializing it, and pushing it to a new private remote. This Skill scripts that entire workflow using the GitHub CLI to ensure the clone and push execute reliably without manual git commands.

Yes, GitHub CLI integration and correct authentication setup are required to clone a private template repository. You must authenticate your GitHub account via the CLI beforehand so the automation script has the permissions needed to create, initialize, and push to the new private repo.

The best way to spin up multiple private clones for development environments is using an automated scripting tool. This Skill handles repository cloning and setup by taking a desired repo name and optional parent directory, then automatically cloning, initializing, and pushing the template content.

Yes, the automated GitHub cloning process creates private repositories that are full-history copies of the specified template. This ensures all previous commits and developmental context are preserved when you spin up new coded environments for testing or further development.

Yes, you can specify an optional parent directory for cloning when creating a new GitHub repository. The automation clones the new private repo into your specified directory, defaulting to a standard location if none is provided, and pushes the initial content automatically.

Automated private repo creation fails during the push step if GitHub CLI authentication is incorrect or lacks permissions. Ensure your GitHub CLI is properly authenticated and has the necessary scopes to create private repositories and push initial content before running the cloning automation.