publish-github

Publish local projects to GitHub with gitleaks hooks and protected branches.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill publish-github
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-github
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/publish-github
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill publish-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically publish a local project to GitHub with built-in security hardening, sensible defaults, and a protected branching model.

Core Features & Use Cases

  • Secrets detection via gitleaks pre-commit hook
  • Comprehensive .gitignore and .gitattributes
  • Protected main branch and development workflow (dev branch)
  • End-to-end automation of repo creation, init, and push

Quick Start

Run this skill to publish your local project to GitHub with security hardening and a ready-to-use development workflow.

Frequently Asked Questions about publish-github

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

FAQPage Schema
How do I publish a local project to GitHub with branch protection and security hardening?▼

Publish a local project to GitHub by automating repository creation, configuring gitleaks pre-commit hooks, setting up .gitignore/.gitattributes, and establishing protected main and dev branches with PR-based workflows.

What is the best way to automate GitHub repository creation and setup a dev branch workflow?▼

Automate GitHub repository creation and dev branch setup by initializing the project, pushing to a new repo, and configuring a protected main branch alongside a dev branch to enforce pull request-based development workflows.

How do I prevent secrets from being committed when automating a GitHub repository push?▼

Prevent secrets from being committed during a GitHub push by configuring a gitleaks pre-commit hook, which automatically scans local changes to detect and block sensitive data before it reaches the remote repository.

Do I need the GitHub CLI and gitleaks installed to automate repo creation and security hardening?▼

Yes, you need the GitHub CLI (gh) and gitleaks installed, alongside a configured Git identity and access to the current project directory, to automate repo creation and apply security hardening.

Can I configure .gitignore and .gitattributes files automatically when publishing to GitHub?▼

Yes, you can configure comprehensive .gitignore and .gitattributes files automatically when publishing to GitHub, ensuring proper handling of line endings and ignored files during the repository initialization process.

Why should I use protected branches and PR workflows for a new GitHub repository?▼

Use protected branches and PR workflows for a new GitHub repository to enforce code review, prevent direct commits to main, and ensure secrets detection via gitleaks runs before any code merges.