agentleFS
Sign inStart free
yaqob3653yaqob3653/vlypse-skills/skills/github-workflow/SKILL.md

github-workflow

Skill1 starsChanged 5 days agoMITView on GitHub

Guidelines for interacting with Git and GitHub, repository conventions, safe branching, committing changes, and asking for permissions when performing destructive actions.

  • Deletes or force-pushes
  • Commits and pushes

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use marketing-psychology, copywriting and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    marketing-psychology

    When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.

    Also in 3 projects that use this

  • SupabaseSkill

    copywriting

    Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 4 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    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 the gh CLI whenever available (gh pr, gh issue, gh repo).

    line 13
  2. Very specific:

    Always specify the repository explicitly when not in a cloned repo root: -R owner/repo.

    line 14
  3. Distinctive:

    Use the standard git command for branch, commit, and local repository operations.

    line 15
  4. Distinctive:

    Never run force-push (git push --force or git push -f) on main, master, or production branches.

    line 20
  5. Distinctive:

    Never delete remote branches without explicit user confirmation.

    line 21
  6. Distinctive:

    Always run git status and git diff before committing to verify changes.

    line 22
  7. Very specific:

    Create feature or fix branches: git checkout -b feat/feature-name or git checkout -b fix/issue-name.

    line 25
  8. Distinctive:

    Keep commits small, focused, and well-described.

    line 26
  9. Very specific:

    Write concise, imperative commit messages (e.g., feat: add user authentication, fix: resolve token refresh loop).

    line 29

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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 & Git Workflow Skill

This skill describes how to interact with Git and GitHub safely within Vlypse. It is authoritative for the usage of the gh CLI and standard git commands.

How to Interact with GitHub

To perform actions on GitHub:

  • Use the gh CLI whenever available (gh pr, gh issue, gh repo).
  • Always specify the repository explicitly when not in a cloned repo root: -R owner/repo.
  • Use the standard git command for branch, commit, and local repository operations.

Safety & Permission Guidelines

  1. Destructive Operations Require Confirmation:
    • Never run force-push (git push --force or git push -f) on main, master, or production branches.
    • Never delete remote branches without explicit user confirmation.
    • Always run git status and git diff before committing to verify changes.
  2. Branching Conventions:
    • Create feature or fix branches: git checkout -b feat/feature-name or git checkout -b fix/issue-name.
    • Keep commits small, focused, and well-described.
  3. Commit Message Format:
    • Write concise, imperative commit messages (e.g., feat: add user authentication, fix: resolve token refresh loop).

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