preview-shots

Étoiles60

Forks3

Mis à jour2 juillet 2026 à 10:56

Open image shots (screenshots, snapshot baselines, montages, renders) in ONE macOS Preview window so the user can eyeball them. Use when the user asks to open / show / pull up / review shots in Preview or Finder, or right after producing visual artifacts the user should look at before signing off.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

dzhng

dzhng/skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

codex

dzhng/skills

Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.

2026-07-0260

eval-skills

dzhng/skills

Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each example input, grade the artifact against the expected outcome, and let the gaps drive the edits. Use when the user wants to test/eval/improve/harden a skill, says "this skill keeps producing X / keeps missing Y", or hands a skill plus example input→expected-output pairs. Pairs with [write-skills](../write-skills/SKILL.md) (the authoring principles every fix obeys).

2026-07-0260

write-skills

dzhng/skills

Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.

2026-07-0260

close-spec

dzhng/skills

When a spec under specs/<feature>/ is done shipping (a feature-slicing build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [feature-slicing](../feature-slicing/SKILL.md) (the plan this closes).

2026-07-0260

feature-slicing

dzhng/skills

Break large features into independently verifiable, human-reviewable slices under specs/<feature>/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates (the browser checkpoints), [refactor-clean](../refactor-clean/SKILL.md) (review the materialized spec so the plan describes one-owner architecture, not the feature bolted on), [screenshot-critique](../../visual/screenshot-critique/SKILL.md) and [compare-screenshots](../../visual/compare-screenshots/SKILL.md) (the visual gates), and a code-review pass (audit each slice before it lands).

2026-07-0260

implement-spec

dzhng/skills

Implement an existing spec. Use when the user says implement spec.

2026-07-0260

name	preview-shots
description	Open image shots (screenshots, snapshot baselines, montages, renders) in ONE macOS Preview window so the user can eyeball them. Use when the user asks to open / show / pull up / review shots in Preview or Finder, or right after producing visual artifacts the user should look at before signing off.

Preview Shots

Put the review-worthy images in front of the user in a single Preview window they can flip through.

Workflow

Curate the set — the images that answer "is this right?": the just-changed or just-blessed baselines, the integrated result, and the reference image when there's something to compare against. Don't dump every PNG in the folder; pick the smallest set that lets the user judge the change. If the user named specific shots, open exactly those.
One window — open them with a single open -a Preview <path> <path> ... call. One open invocation lands all the files in one window with a thumbnail sidebar; separate calls spawn separate windows.
Caption them — list one line per shot (what it is) so the user knows what they're flipping through.

Rules

macOS only (open); pass absolute or repo-root-relative paths.
Order the files most-important-first; the first one is what Preview shows on open.
Review saved PNG/GIF artifacts, not live Chrome. Exact regression capture should run headless by default; only open Chrome when the user explicitly asks for a live browser or when reproducing a headful-only bug.
One set at a time — never pile up windows. Before opening a new set, close any open ones: osascript -e 'tell application "Preview" to close every window'.
Close on unattended proceed. When you opened shots for a non-blocking review and then move on without the user's response, close Preview afterward: osascript -e 'quit app "Preview"'. An overnight autonomous run must never wake the user to a wall of Preview windows — at most one set open, and none once you've proceeded past the checkpoint.