Skip to content
Back to skills

Git Workflow

ASecurity

Use when committing code, pushing branches, writing .gitignore entries, or generating PR metadata. Covers commit format, branch rules, and artifact exclusion.

  • 101 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
code-qualitysqlnodegitapi

Works with

  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add SignalPilot-Labs/AutoFyn --skill git-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/signalpilot-labs-git-workflow/badge)](https://www.skillsdirectory.com/skills/signalpilot-labs-git-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: "Use when committing code, pushing branches, writing .gitignore entries, or generating PR metadata. Covers commit format, branch rules, and artifact exclusion."
---

# Git Workflow

## Commit Format

```
[Round N] <imperative description>
```

Examples:
- `[Round 1] Add user authentication API`
- `[Round 2] Fix N+1 query in dashboard endpoint`
- `[Round 3] Refactor session manager into separate modules`

## Branch Rules

- You are already on the correct working branch. Never create or switch branches.
- Only the orchestrator commits and pushes. Subagents must not run git write commands.
- Push after every commit: `git push origin HEAD`.
- Do NOT create the actual PR — it is created automatically.


## Before Committing

Run `git status` and check for build artifacts. These must NOT be committed:

```
node_modules/   .next/        __pycache__/   *.pyc
dist/           .cache/       build/         *.log
.env            .env.local    *.sqlite       coverage/
```

If `.gitignore` doesn't cover them, add the entries before committing.

## PR Metadata

When the session is ending, generate `/tmp/pr.json` from `git log --oneline` and `git diff --stat`:

```json
{"title": "Short imperative title", "description": "## Summary\n- what and why\n\n## Tests\n- what was tested"}
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…