senternet-site-github-setup

Initializes git repositories, .gitignore files, and GitHub remotes for Vite and Next.js sites.

Updated May 8, 2026
One-click install
npx skills add https://github.com/MattSenter/senternet-site-skills --skill senternet-site-github-setup-mattsenter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senternet-site-github-setup
Source: https://github.com/MattSenter/senternet-site-skills/tree/main/.claude/skills/senternet-site-github-setup
Command: npx skills add https://github.com/MattSenter/senternet-site-skills --skill senternet-site-github-setup-mattsenter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up version control for a new site involves repetitive decisions: what to ignore, how to name branches, how to connect GitHub, and how to avoid committing secrets. This Skill standardizes that entire setup so a new Vite + React + Firebase or Next.js project gets a safe, consistent git and GitHub foundation. ## Core Features & Use Cases - Safe git initialization: Detects existing repos, writes a comprehensive .gitignore covering env files, service account keys, Firebase caches, and editor artifacts, and verifies no secrets are staged before committing. - Branching convention enforcement: Establishes a documented {prefix}/{ticket-id}/{change-summary} branch naming scheme written to .github/CONTRIBUTING.md, adapted for solo or team projects. - GitHub integration: Configures the GitHub MCP server with a fine-grained PAT, falls back to the gh CLI, and optionally creates and pushes to a remote repository. - Use Case: After scaffolding a new marketing site, run this Skill to initialize git, protect credentials from being committed, set up branch conventions, and create a private GitHub remote in one guided flow. ## Quick Start Initialize git and GitHub for my new site project, including a .gitignore that protects my env files and Firebase credentials.

Frequently Asked Questions about senternet-site-github-setup

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

FAQPage Schema
How do I set up git and GitHub for a new Vite React project?▼

Run git init, write a .gitignore covering node_modules, build output, env files, and Firebase artifacts, then create a remote with gh repo create or the GitHub MCP server. Verify with git status that no .env or credential files are staged before the first commit.

What should a .gitignore include for a Firebase web project?▼

Ignore .env files, service-account JSON keys, the .firebase/ cache directory, and debug logs like firebase-debug.log. Commit .firebaserc and firebase.json since they contain project config but no secrets.

Should I use the GitHub MCP server or the gh CLI?▼

The MCP server lets the AI read and write issues, PRs, and repos directly using a fine-grained personal access token stored in ~/.claude.json. The gh CLI is a simpler alternative authenticated via gh auth login; the Skill prefers MCP, then gh, then plain git.

Why does Firebase App Hosting require GitHub setup first on Next.js?▼

Firebase App Hosting builds from a connected GitHub repository and deploys on branch pushes, so firebase apphosting:backends:create fails without a remote and at least one pushed commit. On the Next.js track, git init, remote creation, and pushing main must happen before Firebase setup.

What branch naming convention does this enforce?▼

Branches follow {prefix}/{ticket-id}/{change-summary}: solo developers use feature/ or fix/ prefixes, team members use their first name, and the ticket segment is omitted when no ticket ID exists. Direct commits to main are prohibited.