agentsclimarketplace

Yeet

Skill pinkpixel-dev/skills-collection-2/SKILLS/yeet

Part 2 of the AI and agent skills collection, with 650+ skill folders focused on reusable workflows, security playbooks, cloud implementation guides, scripts, references, and assets for builders and operators.

Install
npx -y skills add pinkpixel-dev/skills-collection-2 --skill yeet

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 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

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

SKILL.md

1.7 KB, 370 tokens by cl100k_base, as published. Nobody here has run it

Prerequisites

  • Require GitHub CLI gh. Check gh --version. If missing, ask the user to install gh and stop.
  • Require authenticated gh session. Run gh auth status. If not authenticated, ask the user to run gh auth login (and re-run gh auth status) before continuing.

Naming conventions

  • Branch: codex/{description} when starting from main/master/default.
  • Commit: {description} (terse).
  • PR title: [codex] {description} summarizing the full diff.

Workflow

  • If on main/master/default, create a branch: git checkout -b "codex/{description}"
  • Otherwise stay on the current branch.
  • Confirm status, then stage everything: git status -sb then git add -A.
  • Commit tersely with the description: git commit -m "{description}"
  • Run checks if not already. If checks fail due to missing deps/tools, install dependencies and rerun once.
  • Push with tracking: git push -u origin $(git branch --show-current)
  • If git push fails due to workflow auth errors, pull from master and retry the push.
  • Open a PR and edit title/body to reflect the description and the deltas: GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head $(git branch --show-current)
  • Write the PR description to a temp file with real newlines (e.g. pr-body.md ... EOF) and run pr-body.md to avoid \n-escaped markdown.
  • PR description (markdown) must be detailed prose covering the issue, the cause and effect on users, the root cause, the fix, and any tests or checks used to validate.

Gives 0 of the 12 instructions most pr commit review skills give in 370 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.