Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
A skill your agent uses when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project.
Install Run Linter
$ npx skills add openshift-examples/web --skill run-linter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-examples/web run-linter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-examples/web.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-linter .claude/skills/run-linter && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "run-linter" agent skill from https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linter into .claude/skills/run-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-linter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linterType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-examples/web --skill run-linter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-examples/web run-linter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-examples/web.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/run-linter .agents/skills/run-linter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-linter" agent skill from https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linter into .agents/skills/run-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-linter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-examples/web --skill run-linter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-examples/web run-linter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-examples/web.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/run-linter .cursor/skills/run-linter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "run-linter" agent skill from https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linter into .cursor/skills/run-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-linter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-examples/web.git --path .agents/skills/run-linter--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-examples/web --skill run-linter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-examples/web run-linter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-examples/web.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/run-linter .gemini/skills/run-linter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "run-linter" agent skill from https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linter into .gemini/skills/run-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-linter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-examples/web run-linterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-examples/web --skill run-linter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-examples/web.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/run-linter .github/skills/run-linter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "run-linter" agent skill from https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linter into .github/skills/run-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-linter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-examples/web --skill run-linter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-examples/web run-linter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-examples/web.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/run-linter .opencode/skills/run-linter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "run-linter" agent skill from https://github.com/openshift-examples/web/tree/main/.agents/skills/run-linter into .opencode/skills/run-linter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-linter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
run-linter- GitHub stars
- 181
- Token cost
- ~240 tokens
- SKILL.md length
- 93 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project.
- Works in 3 steps: Stage or commit all relevant changes → Run the linter → If lint errors are reported, fix them,…
- The user wants to run the linter
- SKILL.md covers Important constraint and Steps
- Calls git
What it does
Run Linter is an agent skill from openshift-examples/web. Use when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project. Covers the requirement to stage/commit changes first.
Its SKILL.md is about 240 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting and Commit messages. It works with Kubernetes. The repository describes itself as: 🚀 Content of examples.openshift.pub.
When your agent uses it
- The user wants to run the linter
- Pre-commit checks
- Markdownlint/yamllint on this project
Example prompts
- “/run-linter”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Stage or commit all relevant changes
- Run the linter
- If lint errors are reported, fix them, stage/commit the fixes, and re-run step 2 until clean.
What it can do on your machine
Read from SKILL.md and the folder at commit 3511549. 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
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
Run Linter loads about 240 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 93 words of instructions outside code blocks.
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
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 93 words (~240 tokens).
“This project uses ./run-local-pre-commit.sh to execute markdownlint and yamllint via pre-commit.”
- name
- run-linter
Files
Just SKILL.md in .agents/skills/run-linter of openshift-examples/web.
Open the folder on GitHubat commit 3511549
Compare with similar skills
Run Linter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Run Linter this skillopenshift-examples/web | 181 | — | ~240 | Automated safety check: Pass | None | |
| Saleor Commit Workflowsaleor/saleor | 23k | — | ~575 | Automated safety check: Pass | BSD-3-Clause | |
| Lint Commit PRTresjs/tres | 3.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.2k | Automated safety check: Notes | Custom licence | |
| Git Commitsdatabasus/databasus | 8.8k | — | ~294 | Automated safety check: Pass | Apache-2.0 | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.3k | Automated safety check: Notes | Custom licence |
Similar skills
Lint Commit PR
Tresjs/tres
Lint local changes, auto-fix, conventional commit, and optionally create PR
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
Git Commits
databasus/databasus
Write Databasus commit messages and branch names using the repository's release-compatible format.
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
Create PR
RLinf/RLinf
Open a GitHub pull request for RLinf, or fix an existing one — checks the PR title against Conventional Commits, writes a precise description that follows .github/PULLREQUESTTEMPLATE.md, and lints…
More from openshift-examples/web
Create Page
openshift-examples/web
Create a new documentation page/chapter in the OpenShift Examples site.
Git Coauthor
openshift-examples/web
A skill your agent uses when committing changes made with AI assistance.
Related
Works with
Categories
Questions about Run Linter
What does Run Linter do?
A skill your agent uses when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project. Run Linter is an agent skill from openshift-examples/web. Use when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project.
When should I use Run Linter?
Run Linter fits situations like: the user wants to run the linter; pre-commit checks; markdownlint/yamllint on this project.
How do I install Run Linter in Claude Code?
Run `npx skills add openshift-examples/web --skill run-linter -a claude-code`. Or copy the skill folder (.agents/skills/run-linter in openshift-examples/web) into .claude/skills/run-linter in your project. Claude Code loads it when a task matches its description.
How do I install Run Linter in Codex?
Run `npx skills add openshift-examples/web --skill run-linter -a codex`. Or copy the skill folder (.agents/skills/run-linter in openshift-examples/web) into .agents/skills/run-linter in your project. Codex loads it when a task matches its description.
Can I use Run Linter in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-examples/web --skill run-linter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-linter, .gemini/skills/run-linter, .github/skills/run-linter and .opencode/skills/run-linter in your project.
What does Run Linter need to run?
Going by SKILL.md and its folder, Run Linter needs the command-line tools its instructions call (git).
Does Run Linter access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Run Linter safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Run Linter use?
No licence was found for Run Linter or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Run Linter use?
About 240 tokens (SKILL.md is roughly 960 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Run Linter?
Skills that share tags, products or a category with Run Linter: Saleor Commit Workflow (saleor/saleor, 23k stars), Lint Commit PR (Tresjs/tres, 3.8k stars), PR Push (icebear0828/codex-proxy, 1.8k stars) and Git Commits (databasus/databasus, 8.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run Linter?
openshift-examples (a GitHub organization) maintains it in openshift-examples/web, which has 181 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 4, 2026.
Source: openshift-examples/web on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.