agentleFS
3akat-system3akat-system/nexus-starter/.claude/skills/git-workflow/SKILL.md

git-workflow

Skill0 starsChanged 6 months agoMITView on GitHub

Git version control workflow. TRIGGER when: commit, git add, git push, закоммить, запушить, создать ветку, create branch, branch, PR, pull request, сохранить изменения в git, save changes in git, version control, git status, что изменилось, what changed, история коммитов, commit history, откатить, rollback. Contains: conventional commits, branch strategy, deploy sequence, rollback.

  • Reads credentials
  • Commits and pushes

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use squad-commands, ci-cd-pipelines and 10 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.
  • Microsoft AzureSkill

    squad-commands

    Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.

    Also in 5 projects that use this

  • harrissohail6Skill

    ci-cd-pipelines

    CI/CD pipeline design and implementation. Auto-activates when discussing deployment, automation, or pipelines.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 4 projects that use this

  • GitHubSkill

    e2e-template-testing

    End-to-end validation of coordinator and agent template changes

    Also in 3 projects that use this

  • GitHubSkill

    notification-routing

    Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding

    Also in 3 projects that use this

  • frostneySkill

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • +5 more from Azure
  • +1 more from github

The file

Files
SKILL.md

Git Workflow

Inspired by: wshobson/commands — adapted for Alexey's projects

Conventional Commits — Message Format

type(scope): brief description

Examples:
feat(auth): add JWT authentication
fix(bot): fix message_callback handling
refactor(routes): extract logic into services
chore(deps): update @maxhub/max-bot-api to 0.3.0
deploy: update staff-bot in production
TypeWhen
featNew feature
fixBug fix
refactorRefactoring without behavior change
choreDependencies, configs, non-code
docsDocumentation
deployDeploy to server

Standard Cycle

# 1. See what changed
git status
git diff

# 2. Add files (not everything — only what is needed)
git add server/routes/feature.js
git add public/app.html
# NOT: git add .env  ← never!

# 3. Commit
git commit -m "feat(feature): add new endpoint"

# 4. Push
git push origin main

# 5. Deploy → see deploy skill

Rolling Back Changes

# Undo last commit (files remain)
git reset --soft HEAD~1

# View a specific commit
git show abc1234

# Restore a file from last commit
git checkout HEAD -- server/routes/auth.js

# Rollback in production (via rsync of old version)
git checkout abc1234  # old commit locally
rsync -avz ... # deploy old version

.gitignore — Mandatory Minimum

node_modules/
.env
.env.local
*.log
dist/
.DS_Store

Pre-Commit Check

# Any secrets in staged files?
git diff --cached | grep -i "password\|token\|secret\|key"

# Status after add
git status

Common Mistakes

MistakeSolution
Committed .envgit rm --cached .env → add to .gitignore → commit
rejected — non-fast-forwardgit pull --rebase → git push
Need to change last commitgit commit --amend -m "new message"

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.