Skip to content

GeiserX/sstack / codex/skills/file-pr

file-pr

Verified

Open a pull request whose title says why the change matters and whose body opens with the problem in the requester's words. Use when asked to file, open, raise or create a PR, or to rewrite a PR's title or description.

Running in Codex

This is the Codex copy of this skill. Read the rest of it with these translations:

  • Agents launched in parallel: spawn each one with spawn_agent before waiting on any, then collect the results with wait_agent. Tell every agent you spawn not to spawn agents of its own. If subagents are unavailable, follow the skill's own rule for that case. Only when it has none, run each lane yourself, one after another.
  • "Your default model" and "your strongest model": spawn the agent with an agent_type whose role file in ~/.codex/agents/ sets model and model_reasoning_effort. An agent without a role runs on the session's model.
  • A slash command such as /name: mention the skill as $name.
  • This repository's hooks and .claude/ paths are for Claude Code only, and nothing here installs a Codex hook. A loop runs one pass per invocation, saves its state and reports how to resume.
  • CLAUDE.md: also read AGENTS.md, which is the file Codex loads.

file-pr

Someone reads a pull request months later, trying to remember why the change exists. The diff already says what changed. The title and body say why it mattered.

Before filing

  1. Look for an existing PR. gh pr list --head <branch>. If one exists, update it instead of opening a second. Done when you know whether this is a new PR or an update.
  2. Read the whole branch diff. git log <base>..HEAD and git diff <base>...HEAD, where the base is the PR's base branch or the repository's default branch. Compare it with what was asked. If the diff drifted from the request, say so instead of filing the drift. Done when every change in the diff belongs to the request.
  3. Learn the house style. Read the last ten merged PR titles and the repository's contributing guide and PR template. Done when you know the title format, and which template sections the repository requires.

The title

The title usually becomes the commit message on the default branch. Write the outcome, not the mechanism, in the repository's format (conventional commits unless it uses another).

Mechanism (avoid)Outcome (write)
perf(server): negotiate per-message deflate on the websocketperf(server): cut websocket frame size by 70% with compression
fix(cli): parse version string in preflightfix(cli): stop the version-drift warning firing when versions match

A title that cannot be written without an implementation detail means the reason for the change is not yet clear. Work it out before filing. No vague subjects (update, cleanup, address feedback) and no trailing period.

The body

Open with the problem as the requester described it: what was broken or missing and why it hurt. Then one or two sentences on what the change does about it. Add a third part only when a reviewer needs it: a surprising choice, a risk, a migration step, a follow-up left undone, or where review should start.

Starting a thread on an existing worktree ignored the new-worktree default, so the preference only worked half the time.

The preference now applies to every new thread.
  • Scale the body to the change. A one-line fix gets two sentences. Stay under about 250 words.
  • Fill the repository's PR template when it has one, keeping its required sections and writing the problem first inside them. Without a template, add no default Summary, Changes or Test Plan headings.
  • Leave out file inventories, command logs, CI output, design history and review history. When refreshing a PR, describe the current full diff, not the sequence of revisions.
  • Reference an issue only when its number is verified from the request, the branch, the commits or the tracker. Fixes #<n> closes it; Refs #<n> only links.
  • A change to any UI must show it in the PR body before the PR is filed: at least one screenshot of the new or changed screen, and a short recording when the change is a flow (several steps, a state that changes, a click that does something). Take them from the real running app, in its dark theme, with no secrets on screen, and say in one sentence what to look at. Upload them as GitHub attachments so they render inline (the github-video-embed recipe works for images too). A UI PR with no image is not ready to file.
  • Keep out customer names, private hostnames, tokens and personal data.
  • Put provenance only in a References section at the end: when the work started in a chat thread or an issue discussion, link the root of that thread, and open each link once before posting to check it lands there. The prose above it states the decision as the team's own.

Filing

  1. When the branch has changes not yet on the remote, stage exact paths, commit and push. A title or description rewrite alone needs no commit.
  2. Run the title and the body through the readable skill. Without it, reread both and cut filler, repeated points and vague wording.
  3. Write the body to a temporary file and pass it with --body-file, so the shell does not mangle it.
  4. Open a ready PR, not a draft, so required checks and review bots run: gh pr create --title "<title>" --body-file <file>. An existing PR is updated with gh pr edit <n> --title "<title>" --body-file <file>.
  5. Never request reviewers on GitHub (--reviewer, the Reviewers box, a re-request after a fix) unless the repository's own rules ask for it.
  6. Report the PR URL. If asked to see it through, follow the checks (gh pr checks <n> --watch) and fix what fails.

Done when the PR exists, its title and body follow this file, and its URL is in the reply.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall