Saleor Commit Workflow

What it does

When your agent uses it

• Committing changes in the Saleor repository
• Resolving ruff, mypy or schema hook failures during a commit
• Regenerating the GraphQL schema or missing migrations that block a commit

Example prompts

• “Commit my changes.”
• “Make a commit for the checkout fix; the pre-commit hooks keep failing on the GraphQL schema.”
• “Commit the new order discount feature and sort out any ruff or mypy errors the hooks raise.”

Requirements

• A Saleor checkout with a `.venv` virtual environment
• Git with the project's pre-commit hooks installed

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Activate virtual env: source .venv/bin/activate (look for .venv dir in project root)
2. 2Run git status and git diff (staged + unstaged) to understand all changes
3. 3Stage relevant files with git add (specific files, not git add -A)
4. 4Write a comprehensive commit message describing what changed and why
5. 5Run git commit
6. 6If pre-commit hooks fail, follow error resolution below and retry

What it can do on your machine

Read from SKILL.md and the folder at commit 782a751. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • python

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Saleor Commit Workflow loads about 575 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 207 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~87

When it runs · the whole SKILL.md, loaded when a task matches

~575

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from saleor/saleor at commit 782a751, republished under its BSD-3-Clause licence (© saleor). 207 words, ~575 tokens.

name

saleor-commit

description

Commit changes in the Saleor codebase with pre-commit hook error handling. Use when asked to "commit", "commit changes", "make a commit", or any git commit task in the Saleor project. Handles virtual env activation, staging, commit message writing, and automatic resolution of pre-commit hook failures (ruff, mypy, schema, migrations).

git commit -m "$(cat <<'EOF'
Short summary of changes

Detailed description of what was changed and why.
List specific modifications when multiple files are affected.

EOF
)"

python manage.py get_graphql_schema > saleor/graphql/schema.graphql
git add saleor/graphql/schema.graphql

python manage.py makemigrations
git add saleor/**/migrations/*.py

© saleor, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/saleor-commit of saleor/saleor.

Open the folder on GitHubat commit 782a751