Thrunt pr branch
Skill 3dcom2711/thrunt-god/thrunt-god/examples/brute-force-to-persistence/.github/skills/thrunt-pr-branch
Run threat hunting workflows for agentic IDEs like Claude Code, OpenCode, and Gemini in one command
npx -y skills add 3dcom2711/thrunt-god --skill thrunt-pr-branchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create a clean PR branch by filtering out .planning/ commits — ready for code review
SKILL.md
0.7 KB, 125 tokens by cl100k_base, as published. Nobody here has run it
This solves the problem of PR diffs being cluttered with PLAN.md, SUMMARY.md, STATE.md changes that are irrelevant to code review. </objective>
<execution_context> @.github/thrunt-god/workflows/pr-branch.md </execution_context>
<process> Execute the pr-branch workflow from @.github/thrunt-god/workflows/pr-branch.md end-to-end. </process>What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most pr commit review skills give in 125 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07
- Use conventional commits formatin 127 of 888, across 115 files
- Keep subject line under 72 charactersin 62 of 888, across 48 files
- Delete branches after mergein 51 of 888, across 38 files
- Use imperative mood in subject linein 51 of 888, across 42 files
- Use imperative mood in commit messagesin 44 of 888
- Verify directory is ignored before creating worktreein 43 of 888, across 12 files
- Generate a conventional commit messagein 43 of 888
- Add unignored worktree directories to gitignorein 42 of 888, across 10 files
- Make atomic commitsin 39 of 888, across 27 files
- Run tests before committingin 36 of 888, across 25 files
- Verify clean test baselinein 35 of 888, across 9 files
- Split unrelated changes into separate commitsin 35 of 888, across 30 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.