Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

update-ref

Estrelas0

Forks0

Atualizado8 de março de 2026 às 15:39

Updates the pinned SHA for an existing audit reference. Use when the user wants to upgrade or downgrade a ref to a different commit, asks to pull in new changes from an upstream repo, or wants to pin a ref to a specific SHA. Do NOT use for adding a brand new ref (use add-ref) or removing a ref entirely (use remove-ref).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

mishoko

mishoko/web3-audit-ref

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	update-ref
description	Updates the pinned SHA for an existing audit reference. Use when the user wants to upgrade or downgrade a ref to a different commit, asks to pull in new changes from an upstream repo, or wants to pin a ref to a specific SHA. Do NOT use for adding a brand new ref (use add-ref) or removing a ref entirely (use remove-ref).
allowed-tools	["Bash","Read","Grep"]

Update Pinned Reference

Before running

Confirm with the user:

The ref name to update (must exist under audit-refs/)
The target SHA — or approval to use latest remote HEAD

Run

.claude/skills/update-ref/update_ref.sh <ref-name> [<new-sha>]

After the script finishes

The script stages all changes, prints the diff, and suggests a commit message. It does not commit.

Present the script's output to the user (it already contains the staged diff).
Wait for explicit commit approval before proceeding.
Use the commit message the script suggests.

Mais deste repositório

mesmo repositório

hydrate-pins

mishoko/web3-audit-ref

Initializes and pins all audit reference submodules after a fresh clone. Use when the user has just cloned the repository and needs to set up the submodules, or when submodules are missing or uninitialized. Do NOT use to update a ref to a new SHA (use update-ref) or to add a new ref (use add-ref).

2026-03-080

add-ref

mishoko/web3-audit-ref

Adds a new pinned audit reference (git submodule) to this repository. Use when the user wants to add an external repository as an audit reference, provides a GitHub URL to add, or asks to pin a new tool or methodology. Do NOT use for updating an existing ref's SHA (use update-ref) or re-adding a previously removed ref without explicit user confirmation.

2026-03-080

remove-ref

mishoko/web3-audit-ref

Removes a pinned audit reference from this repository. Use when the user explicitly asks to remove, delete, or retire an audit reference. Requires a stated reason before proceeding. Do NOT use for updating a ref's SHA (use update-ref) or temporarily disabling a ref.

2026-03-080

scan-ref

mishoko/web3-audit-ref

Scans an audit reference for dangerous patterns: install hooks, encoded payloads, curl-pipe-bash, symlinks, git hooks, suspicious Makefiles, and other supply-chain threats. Use before adding or updating a ref, or on-demand to audit an existing ref. Does NOT modify any files.

2026-03-080

name	update-ref
description	Updates the pinned SHA for an existing audit reference. Use when the user wants to upgrade or downgrade a ref to a different commit, asks to pull in new changes from an upstream repo, or wants to pin a ref to a specific SHA. Do NOT use for adding a brand new ref (use add-ref) or removing a ref entirely (use remove-ref).
allowed-tools	["Bash","Read","Grep"]

Update Pinned Reference

Before running

Confirm with the user:

The ref name to update (must exist under audit-refs/)
The target SHA — or approval to use latest remote HEAD

Run

.claude/skills/update-ref/update_ref.sh <ref-name> [<new-sha>]

After the script finishes

The script stages all changes, prints the diff, and suggests a commit message. It does not commit.

Present the script's output to the user (it already contains the staged diff).
Wait for explicit commit approval before proceeding.
Use the commit message the script suggests.