agentleFS
Sign inStart free
matheus-rib1108matheus-rib1108/claude-skills-br/skills/github-helper/SKILL.md

github-helper

Skill0 starsChanged 28 days agoMITView on GitHub

Does everything Git and GitHub for the user — creates repositories, first commit and push, branches, pull requests, releases, GitHub Pages, and turns on GitHub's free security features (Dependabot, secret scanning, CodeQL, branch protection). Use when the user asks "cria um Git/repositório", "sobe pro GitHub", "faz um PR", "salva no GitHub", "organiza meu GitHub", or starts a new project.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Use whatever is available, in this order: GitHub MCP tools (mcp__github__*) → gh CLI (gh auth status.

    line 8
  2. Distinctive:

    Create the repo (private by default unless the user wants it public), push main.

    line 14
  3. Distinctive:

    Never commit secrets. If one was committed: rotate the key first, then clean history.

    line 20
  4. Very specific:

    Before pushing: run the project's lint/tests.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub helper

Use whatever is available, in this order: GitHub MCP tools (mcp__github__*) → gh CLI (gh auth status; if not logged in, the user runs gh auth login once) → plain git.

New project

  1. git init, sensible .gitignore (include .env*, node_modules, build output), README in Portuguese with what it is and how to run it.
  2. Create the repo (private by default unless the user wants it public), push main.
  3. Turn on security for every new repo:
    • Dependabot alerts + security updates (.github/dependabot.yml for npm/pip, weekly).
    • Secret scanning + push protection (Settings → Code security; free on public repos).
    • CodeQL default setup (gh api -X PATCH repos/{owner}/{repo}/code-scanning/default-setup -f state=configured).
    • Branch protection on main: require PR + passing checks for client projects.
  4. Never commit secrets. If one was committed: rotate the key first, then clean history.

Daily work

  • Work on a branch, small commits with clear messages, PR to main, merge when CI is green.
  • Before pushing: run the project's lint/tests; for sites, site-fortress before a release.
  • Releases: tag vX.Y.Z + short changelog.

Deploys from GitHub

Vercel/Netlify/Cloudflare connect to the repo and deploy each push (preview per PR). Static sites can also use GitHub Pages (gh api -X POST repos/{owner}/{repo}/pages ...).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free