Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
A skill your agent uses for any honk change to plan, review, verify and prepare the PR.
GPL-3.0Auto-check passed
Install Honk Change
$ npx skills add daeuniverse/honk --skill honk-change -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install daeuniverse/honk honk-change --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/daeuniverse/honk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/honk-change .claude/skills/honk-change && 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 "honk-change" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-change into .claude/skills/honk-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-change", 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/daeuniverse/honk/tree/main/.agents/skills/honk-changeType 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 daeuniverse/honk --skill honk-change -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install daeuniverse/honk honk-change --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/honk-change .agents/skills/honk-change && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "honk-change" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-change into .agents/skills/honk-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-change", 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 daeuniverse/honk --skill honk-change -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install daeuniverse/honk honk-change --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/honk-change .cursor/skills/honk-change && 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 "honk-change" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-change into .cursor/skills/honk-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-change", 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/daeuniverse/honk.git --path .agents/skills/honk-change--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 daeuniverse/honk --skill honk-change -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install daeuniverse/honk honk-change --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/honk-change .gemini/skills/honk-change && 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 "honk-change" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-change into .gemini/skills/honk-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-change", 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 daeuniverse/honk honk-changeInstalls 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 daeuniverse/honk --skill honk-change -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/honk-change .github/skills/honk-change && 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 "honk-change" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-change into .github/skills/honk-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-change", 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 daeuniverse/honk --skill honk-change -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install daeuniverse/honk honk-change --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daeuniverse/honk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/honk-change .opencode/skills/honk-change && 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 "honk-change" agent skill from https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-change into .opencode/skills/honk-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honk-change", 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
honk-change- GitHub stars
- 156
- Token cost
- ~558 tokens
- SKILL.md length
- 318 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses for any honk change to plan, review, verify and prepare the PR.
- Works in 8 steps: Plan first, in a file or draft PR text.… → Inventory the impact of each contract… → Have a second mind review the plan… → …
- Any honk change to plan
- SKILL.md covers Steps and Checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Honk Change is an agent skill from daeuniverse/honk. Use for any honk change to plan, review, verify and prepare the PR.
Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Inspired by dae & sing-box, it's an ebpf based proxy with clash-api. The licence is GPL-3.0.
When your agent uses it
- Any honk change to plan
- Verify and prepare the PR
Example prompts
- “/honk-change”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Plan first, in a file or draft PR text. Name the failing input and the line producing it at origin/main, with its SHA. Write one…
- Inventory the impact of each contract touched: users in other crates, tests and benches that construct it directly, CI workflows that run…
- Have a second mind review the plan before code.
- One commit per step: AGENTS.md, "Code style guidelines".
- Verification and reporting: AGENTS.md, "Testing instructions" and "Current validation guidance". For input-to-structure code, also compare…
- Have a reader who has not seen the plan read the diff and write what a user would experience differently.
- PR text: AGENTS.md, "Code style guidelines" (PR bodies).
- Batch same-theme few-line fixes in one PR with one commit each. Put edge findings in the rolling tracker issue and serious reproducible…
What it can do on your machine
Read from SKILL.md and the folder at commit a8a74a4. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Honk Change loads about 558 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 318 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
The full file from daeuniverse/honk at commit a8a74a4, republished under its GPL-3.0 licence (© daeuniverse). 318 words, ~558 tokens.
Download SKILL.mdSave it as
.claude/skills/honk-change/SKILL.md (or your agent's skills folder).- name
- honk-change
- description
- Use for any honk change to plan, review, verify and prepare the PR.
Read first: AGENTS.md and the rules files its Task routing table names for the contracts touched.
Steps
- Plan first, in a file or draft PR text. Name the failing input and the line producing it at
origin/main, with its SHA. Write one imperative sentence per commit and say what is deliberately left alone. Tests:AGENTS.md, "Testing instructions". For a non-behavioural change (docs, workflow, extraction), say why reproduction and hunk ablation do not apply. Name the substitute check: byte comparison, link check or workflow stub. - Inventory the impact of each contract touched: users in other crates, tests and benches that construct it directly, CI workflows that run them, pages in
doc/en/anddoc/zh/, and any second implementation. Mark each changed, checked unaffected or left as a finding. If the change reaches another module, change that module rather than leaving a shim. - Have a second mind review the plan before code.
- One commit per step:
AGENTS.md, "Code style guidelines". - Verification and reporting:
AGENTS.md, "Testing instructions" and "Current validation guidance". For input-to-structure code, also compare a fixed input set before and after. List every changed output and its reason. - Have a reader who has not seen the plan read the diff and write what a user would experience differently.
- PR text:
AGENTS.md, "Code style guidelines" (PR bodies). - Batch same-theme few-line fixes in one PR with one commit each. Put edge findings in the rolling tracker issue and serious reproducible defects in their own issues.
Checklist
- Plan records the input, source revision, commits, exclusions and applicable check.
- Impact inventory gives every consumer a disposition.
- A second mind reviewed the plan before code.
- Commit steps follow "Code style guidelines".
- Verification follows the named root sections; input-to-structure comparisons account for changed outputs.
- A reader without the plan described the diff's user-visible effects.
- PR text follows "Code style guidelines".
- Fixes and findings are batched by step 8.
© daeuniverse, GPL-3.0. 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 .agents/skills/honk-change of daeuniverse/honk.
Open the folder on GitHubat commit a8a74a4
Compare with similar skills
Honk Change 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 |
|---|---|---|---|---|---|---|
| Honk Change this skilldaeuniverse/honk | 156 | — | ~558 | Automated safety check: Pass | GPL-3.0 | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| Release PreparationCherryHQ/cherry-studio | 53k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| Prepare Paperclip PRpaperclipai/paperclip | 99k | — | ~954 | Automated safety check: Pass | MIT | |
| Prepare MCP Integrationpaperclipai/paperclip | 99k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Prepare PRmengxi-ream/read-frog | 10k | — | ~1.3k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
Prepare Paperclip PR
paperclipai/paperclip
Prepare a Paperclip branch for PR with commits, template body, and checks.
Prepare MCP Integration
paperclipai/paperclip
Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection.
Prepare PR
mengxi-ream/read-frog
Prepare all work before creating a pull request, optionally for the issue provided as argument
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
More from daeuniverse/honk
Honk Real Ebpf Tests
daeuniverse/honk
A skill your agent uses to choose native Linux, CI-shaped VM or unavailable-environment paths for real eBPF tests.
Honk Config Change
daeuniverse/honk
A skill your agent uses for configuration contracts, parsers, reference docs and their core or outbound consumers.
Honk Release
daeuniverse/honk
A skill your agent uses to prepare a honk release and follow the maintainer's tag and publication sequence.
Questions about Honk Change
What does Honk Change do?
A skill your agent uses for any honk change to plan, review, verify and prepare the PR. Honk Change is an agent skill from daeuniverse/honk. Use for any honk change to plan, review, verify and prepare the PR.
When should I use Honk Change?
Honk Change fits situations like: any honk change to plan; verify and prepare the PR.
How do I install Honk Change in Claude Code?
Run `npx skills add daeuniverse/honk --skill honk-change -a claude-code`. Or copy the skill folder (.agents/skills/honk-change in daeuniverse/honk) into .claude/skills/honk-change in your project. Claude Code loads it when a task matches its description.
How do I install Honk Change in Codex?
Run `npx skills add daeuniverse/honk --skill honk-change -a codex`. Or copy the skill folder (.agents/skills/honk-change in daeuniverse/honk) into .agents/skills/honk-change in your project. Codex loads it when a task matches its description.
Can I use Honk Change 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 daeuniverse/honk --skill honk-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/honk-change, .gemini/skills/honk-change, .github/skills/honk-change and .opencode/skills/honk-change in your project.
What does Honk Change need to run?
SKILL.md names no scripts, command-line tools or credentials: Honk Change is instructions for the agent only.
Does Honk Change access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Honk Change 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 Honk Change use?
Honk Change is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Honk Change use?
About 558 tokens (SKILL.md is roughly 2.2k 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 Honk Change?
Skills that share tags, products or a category with Honk Change: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), Release Preparation (CherryHQ/cherry-studio, 53k stars), Prepare Paperclip PR (paperclipai/paperclip, 99k stars) and Prepare MCP Integration (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Honk Change?
daeuniverse (a GitHub organization) maintains it in daeuniverse/honk, which has 156 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.
Source: daeuniverse/honk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.