agentleFS
UfukCetinkaya57UfukCetinkaya57/backend-governance/.claude/skills/commit/SKILL.md

commit

Skill0 starsChanged 5 months agoMITView on GitHub

Governance kurallarına uygun commit yapar

  • Reads credentials

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use act-on-feedback, generate-run-commands 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.
  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 4 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 4 projects that use this

  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MindgamesSkill

    branch

    Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

    Also in 9 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Migration varsa: commit mesajinda acikca belirt.

    line 80
  2. Distinctive:

    Commit mesaji HEREDOC ile olusturulur (format korumasi icin)

    line 89

“Common” is measured: kept by at least 6 in 10 of the 167 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

Governance Commit

Governance kurallarına uygun commit olustur. Kurallar:

Adimlar

1. Degisiklikleri Kontrol Et

git status
git diff --cached --name-only  (staged dosyalar)
git diff --name-only           (unstaged dosyalar)

2. Governance Dosyalarini HARIC TUT

Asagidaki dosyalar/klasorler commit'e DAHIL EDILMEZ — staged ise unstage et:

  • .claude/ (agents, rules, skills, settings)
  • CLAUDE.md (kok dizindeki)
  • backend-governance/ (klasor veya symlink)
  • proje/ (proje profilleri)
git reset HEAD -- .claude/ CLAUDE.md backend-governance/ proje/ 2>/dev/null

3. Hassas Dosyalari ENGELLE

Asagidaki dosyalar commit'e ALINMAZ. Staged ise unstage et ve UYAR:

  • .env, .env.*
  • *credentials*, *secret*
  • *.pem, *.key

4. Dosya Encoding Kontrolu (dosya-tipine gore)

BOM politikasi dosya tipine gore AYRISIR. "Hepsine BOM ekle" YANLIS — config dosyalarini kirar (bkz. memory feedback_no_bom_tool_config).

BOM-LU olmali (ilk 3 byte EF BB BF):

  • *.cs (.NET / Visual Studio BOM'lu UTF-8 uretir, repo normu)

BOM-SUZ olmali (BOM parser'i / araci kirar):

  • *.yml, *.yaml, *.json, .env, .env.*
  • Dockerfile, docker-compose*.yml, Caddyfile
  • *.sh, *.sql, *.csproj, *.props, *.targets
  • *.md (governance dahil)

Kontrol: head -c3 <dosya> | od -An -tx1 (ef bb bf => BOM var)

Duzeltme (tip-ayrimli: .cs'e ekle, config'ten cikar — iki AYRI cagri):

python3 -c "
import sys
mode = sys.argv[1]   # 'add' (.cs icin) veya 'strip' (config icin)
for f in sys.argv[2:]:
    c = open(f,'rb').read()
    has = c.startswith(b'\xef\xbb\xbf')
    if mode=='add' and not has:
        open(f,'wb').write(b'\xef\xbb\xbf'+c); print('BOM eklendi:', f)
    if mode=='strip' and has:
        open(f,'wb').write(c[3:]); print('BOM cikarildi:', f)
" add   <degisen .cs dosyalari>
# ayri cagri config icin:
# python3 -c "...ayni script..." strip <degisen config dosyalari>

Not: Binary dosyalar (resim, font, zip) haric. BOM islemi eol'e DOKUNMAZ (yalniz ilk 3 byte'a bakar). .gitattributes KULLANILMIYOR (bilincli — renormalize riski; bu kontrol commit oncesi tek enforcement noktasi).

5. Commit Mesaji Olustur

  • Kullanici mesaj verdiyse ($ARGUMENTS) onu kullan
  • Vermediyse diff'e bakarak kisa, anlasilir mesaj yaz
  • Insan yazmis gibi olmali — AI ciktisi formati YASAK
  • Turkce veya Ingilizce (projenin diline gore)
  • Conventional commits formati opsiyonel ama tercih edilir (feat:, fix:, refactor:)
  • Migration varsa: commit mesajinda acikca belirt. Ornek: feat: kullanici tablosuna phone_number alani eklendi (migration gerekli)
  • Migration iceren commit'lerde mesajda su bilgiler yer almali:
    • Hangi tablo/alan etkileniyor
    • Migration dosyasinin adi (varsa)
    • Rollback gerektirip gerektirmedigi

6. Commit Kurallari

  • Co-Authored-By satiri EKLENMEZ — ASLA
  • --no-verify kullanilmaz (hook'lar atlanmaz)
  • Commit mesaji HEREDOC ile olusturulur (format korumasi icin)

7. Commit Et ve Dogrula

git add <dosyalar>
git commit -m "mesaj"
git status  # dogrulama

8. Raporla

  • Commit edilen dosyalar
  • Haric tutulan governance dosyalari (varsa)
  • Engellenen hassas dosyalar (varsa)
  • BOM eklenen dosyalar (varsa)
  • Migration bilgisi (varsa)

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.