agentleFS
Sign inStart free
kecoma1kecoma1/MQL5-SKILLS/skills/git/SKILL.md

git

Skill17 starsChanged 7 months agoMITView on GitHub

Use when creating branches, writing commits, or following repository Git conventions in this workspace. Follow the local branch naming and commit message patterns, including issue references when available.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sql, databases 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.
  • thechandanbhagatSkill

    sql

    Write SQL queries, optimize database performance, design schemas, and debug SQL issues. Use for database operations, query optimization, and schema design.

    Also in 4 projects that use this

  • mrgoonieSkill

    databases

    Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.

    Also in 3 projects that use this

  • mrgoonieSkill

    devops

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.

    Also in 4 projects that use this

  • MicrosoftSkill

    typescript

    TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.

    Also in 4 projects that use this

  • VercelSkill

    react

    React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 8 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 16 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 16

    Distinctive

    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
  1. Distinctive:

    Use this skill when the user asks for help with branches, commits, or Git naming conventions in this repository.

    line 8
  2. Distinctive:

    Create short, lowercase branch names with hyphens.

    line 12
  3. Distinctive:

    Use one of these prefixes:

    line 13
  4. Distinctive:

    Use this format for commit subjects:

    line 47
  5. Distinctive:

    When there is a related issue, add a blank line and reference it like this:

    line 59
  6. Distinctive:

    Use these commit types:

    line 69
  7. Distinctive:

    Use a short scope that matches the affected area.

    line 84
  8. Distinctive:

    Keep the summary short and action-oriented.

    line 96
  9. Distinctive:

    Use lowercase unless a term requires uppercase.

    line 98
  10. Distinctive:

    Do not end the summary with a period.

    line 99
  11. Distinctive:

    Prefer specific outcomes over vague wording.

    line 100
  12. Distinctive:

    Use issue references when the repository tracks work with issue IDs.

    line 116
  13. Very specific:

    Use refs #issue-id when the commit relates to an issue

    line 118
  14. Very specific:

    Use closes #issue-id when the commit is intended to close the issue

    line 119
  15. Distinctive:

    When preparing multiple commits for one branch:

    line 137
  16. Distinctive:

    do not mix unrelated changes in the same commit

    line 140
  17. Distinctive:

    keep the branch name aligned with the main intent of the work

    line 141
  18. Distinctive:

    If the work is small and tightly related, prefer one clean commit over many noisy commits.

    line 143

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

Git

Use this skill when the user asks for help with branches, commits, or Git naming conventions in this repository.

Branch Names

Create short, lowercase branch names with hyphens. Use one of these prefixes:

  • feature/branch-name
  • bug/branch-name
  • hotfix/branch-name
  • chore/branch-name
  • docs/branch-name
  • refactor/branch-name
  • test/branch-name

Choose the prefix by intent:

  • feature/ for new functionality
  • bug/ for defect fixes that are not urgent production fixes
  • hotfix/ for urgent fixes
  • chore/ for maintenance, config, tooling, or cleanup
  • docs/ for documentation-only changes
  • refactor/ for structural code improvements without intended behavior change
  • test/ for test-only additions or fixes

Examples:

feature/add-git-skill
bug/fix-backtest-report-path
hotfix/repair-mt5-launch-command
chore/normalize-skill-path-placeholders
docs/update-run-backtests-skill
refactor/simplify-fvg-loader
test/add-backtest-config-coverage

Commit Format

Use this format for commit subjects:

type(scope): summary

Preferred example:

feat(skills): add git conventions skill

When there is a related issue, add a blank line and reference it like this:

feat(skills): add git conventions skill

refs #123

Commit Types

Use these commit types:

  • feat for new behavior or new functionality
  • fix for bug fixes
  • hotfix for urgent production fixes when the repository uses a distinct hotfix commit type
  • chore for maintenance or tooling updates
  • docs for documentation changes
  • refactor for internal code restructuring without intended behavior change
  • test for test changes
  • perf for performance improvements
  • build for build pipeline or dependency packaging changes
  • ci for CI workflow changes

Scope

Use a short scope that matches the affected area.

Examples:

  • skills
  • backtests
  • compile
  • mt5
  • docs

Summary Rules

Keep the summary short and action-oriented.

  • Use lowercase unless a term requires uppercase.
  • Do not end the summary with a period.
  • Prefer specific outcomes over vague wording.

Good:

fix(backtests): use placeholder report path in ini example

Avoid:

fix(stuff): various updates

Issue References

Use issue references when the repository tracks work with issue IDs.

  • Use refs #issue-id when the commit relates to an issue
  • Use closes #issue-id when the commit is intended to close the issue

Examples:

fix(mt5): handle missing tester log gracefully

refs #45
docs(skills): clarify branch naming rules

closes #52

Pull Request Alignment

When preparing multiple commits for one branch:

  • keep commits focused
  • do not mix unrelated changes in the same commit
  • keep the branch name aligned with the main intent of the work

If the work is small and tightly related, prefer one clean commit over many noisy commits.

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