agentleFS
saleorsaleor/saleor-dashboard/.claude/skills/pinact/SKILL.md

pinact

Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub

Read pinact's documentation with `pinact docs list` and `pinact docs show <name>` before answering. pinact is a CLI that pins GitHub Actions and reusable workflows to full commit SHAs, updates them, and verifies their version comments. Use for any question about pinact, `PINACT_*` environment variables, `pinact run` / `init` / `migrate` / `token`, the configuration file `.pinact.yaml`, pinact's exit codes, or errors from pinact. Use it too when a workflow fails a pinact check in CI, or when an action isn't pinned and it isn't clear why.

1 other project uses a version of this, 1 of them edited.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 33 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the saleor/saleor-dashboard repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about saleor/saleor-dashboard

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Don't answer from your training knowledge about pinact itself - its commands, flags, environment variables, configuration, or what its …

    line 15
  2. Distinctive:

    Read the source only after the documentation has failed to answer the question, and read it at the version that is installed - a repository …

    line 32
  3. Very specific:

    If pinact docs is rejected as an unknown command, the installed pinact is older than v5.0.0.

    line 41
  4. Very specific:

    If pinact is not installed at all, point them at the install guide:

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Don't answer from your training knowledge about pinact itself - its commands, flags, environment variables, configuration, or what its errors mean. Run pinact docs list to list the documentation, then pinact docs show <name> to read the relevant topics before answering questions about pinact or troubleshooting its errors. pinact docs show prints the whole topic; read it through before concluding. You don't need to re-read a topic you already read in this session.

pinact run edits the files it is given. When you only want to know whether a repository is pinned, run pinact run --check, which reports without editing. Don't run pinact run --update on the user's behalf unless they asked for an update: it changes which version of an action a workflow uses.

A non-zero exit code is not necessarily pinact failing. 1 means something needs pinning, 2 means an action pinact can't fix by itself, and 3 means pinact itself failed. Read pinact docs show exit_codes before calling a run broken, and follow it to the topic for the specific case, such as codes/005 for a SHA pinned without a version comment.

Read the source only after the documentation has failed to answer the question, and read it at the version that is installed - a repository checkout is usually main, which can be far ahead of the binary the user runs.

Organization-specific practice - which actions a repository is allowed to use, whether updates go through Renovate, and so on - is outside what pinact docs covers, so answer that from the user's own documentation and the conversation. When the two disagree about how pinact itself behaves, pinact docs wins.

If pinact docs is rejected as an unknown command, the installed pinact is older than v5.0.0. Tell the user to upgrade, and don't fall back to guessing.

If pinact is not installed at all, point them at the install guide:

https://github.com/suzuki-shunsuke/pinact/blob/main/INSTALL.md

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.