Codewhale Dogfood Install
codewhale-hq/Codewhale
Proves a Codewhale change in the real product: a stamped release build, an atomic local install, fresh-shell verification and manual QA that automated gates cannot cover.
Picks up bugs a person flagged by pointing at elements in the running app, each mark carrying the element, their note and the source file and line, then fixes and verifies them.
$ npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install reticlehq/reticle fix-what-i-pointed-at --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/reticlehq/reticle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fix-what-i-pointed-at .claude/skills/fix-what-i-pointed-at && 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 "fix-what-i-pointed-at" agent skill from https://github.com/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-at into .claude/skills/fix-what-i-pointed-at/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-what-i-pointed-at", 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/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-atType 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 reticlehq/reticle --skill fix-what-i-pointed-at -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install reticlehq/reticle fix-what-i-pointed-at --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/reticlehq/reticle.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/fix-what-i-pointed-at .agents/skills/fix-what-i-pointed-at && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fix-what-i-pointed-at" agent skill from https://github.com/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-at into .agents/skills/fix-what-i-pointed-at/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-what-i-pointed-at", 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 reticlehq/reticle --skill fix-what-i-pointed-at -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install reticlehq/reticle fix-what-i-pointed-at --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/reticlehq/reticle.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/fix-what-i-pointed-at .cursor/skills/fix-what-i-pointed-at && 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 "fix-what-i-pointed-at" agent skill from https://github.com/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-at into .cursor/skills/fix-what-i-pointed-at/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-what-i-pointed-at", 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/reticlehq/reticle.git --path skills/fix-what-i-pointed-at--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 reticlehq/reticle --skill fix-what-i-pointed-at -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install reticlehq/reticle fix-what-i-pointed-at --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/reticlehq/reticle.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/fix-what-i-pointed-at .gemini/skills/fix-what-i-pointed-at && 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 "fix-what-i-pointed-at" agent skill from https://github.com/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-at into .gemini/skills/fix-what-i-pointed-at/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-what-i-pointed-at", 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 reticlehq/reticle fix-what-i-pointed-atInstalls 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 reticlehq/reticle --skill fix-what-i-pointed-at -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/reticlehq/reticle.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/fix-what-i-pointed-at .github/skills/fix-what-i-pointed-at && 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 "fix-what-i-pointed-at" agent skill from https://github.com/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-at into .github/skills/fix-what-i-pointed-at/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-what-i-pointed-at", 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 reticlehq/reticle --skill fix-what-i-pointed-at -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install reticlehq/reticle fix-what-i-pointed-at --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/reticlehq/reticle.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/fix-what-i-pointed-at .opencode/skills/fix-what-i-pointed-at && 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 "fix-what-i-pointed-at" agent skill from https://github.com/reticlehq/reticle/tree/main/skills/fix-what-i-pointed-at into .opencode/skills/fix-what-i-pointed-at/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-what-i-pointed-at", 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.
fix-what-i-pointed-atPicks up bugs a person flagged by pointing at elements in the running app, each mark carrying the element, their note and the source file and line, then fixes and verifies them.
Reticle's running app has a Flag a bug control: a person clicks it, points at an element and types what is wrong. Each flag becomes a mark that carries the element, the note and a file and line pointer, so the usual cycle of screenshot, description and clarifying questions collapses into one call. The skill drains the marks with reticle_session in review mode, at the start of a session and again whenever the person has been in the app. Reading never consumes a mark.
The loop is read, open, fix, verify, resolve. The agent groups marks that point at the same file, opens source.file at source.line, fixes what the note asks, and verifies in the running app by re-driving the control with reticle_act_and_wait or inspecting the element with reticle_look instead of eyeballing it. Only then does it resolve the mark. A mark that cannot be fixed is left open with an explanation, and if a note describes intended behavior, the agent says so and lets the person decide. Reports use the person's wording, such as the Pay button on checkout, instead of file paths.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 178e5c0. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npxcurlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
docs.reticle.shFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Fix What I Pointed At loads about 878 tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 397 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.
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.
The full file from reticlehq/reticle at commit 178e5c0, republished under its Apache-2.0 licence (© reticlehq). 397 words, ~878 tokens.
.claude/skills/fix-what-i-pointed-at/SKILL.md (or your agent's skills folder)."The spacing on that card is wrong" is unactionable in chat and precise in the app. Reticle's running app has a Flag a bug control: the human clicks it, points at an element, and types what is wrong. Each flag becomes a mark carrying the element, the note, and the file:line, so the round trip that usually costs a screenshot, a description, and two clarifying questions costs one call.
Not installed? RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init, then the install-and-verify skill.
reticle_session({ action: "review", sessionId }){
"marks": [
{
"id": "m1",
"note": "this button is misaligned",
"label": "button \"Pay\"",
"source": { "file": "src/Checkout.tsx", "line": 42 },
"fix": "Open src/Checkout.tsx:42 and fix: this button is misaligned."
}
],
"pendingCount": 1
}Check this at the start of a session, and again whenever the human has been in the app. Reading never consumes a mark, so list → fix → verify → resolve is safe to run in any order.
source.file at source.line. This is the whole point: no hunting for which component rendered that button.note asks for. If the note is ambiguous, the element label and its source usually disambiguate it. Ask the human only when they genuinely do not.reticle_act_and_wait and name the consequence, or reticle_look { action: "element" } on the element for a layout or theme complaint. A visual fix confirmed by looking at it is how the mark gets reopened.reticle_session({ action: "review", sessionId, resolve: "m1" })Resolve only after the fix is verified. A resolved mark is a promise to the human that the thing they pointed at is done.
Say so against that mark and leave it unresolved. A mark silently dropped is worse than an open one: the human believes it was handled and finds out later. If the note describes intended behaviour rather than a bug, say that too, and let them decide.
They pointed at "that button". Report on "the Pay button on checkout", with what you changed and the evidence it now works. Marks come from people who are looking at the screen, not at the repo, so a report full of file paths and no user-facing language answers the wrong question.
Everything else: curl https://docs.reticle.sh/llms.txt. If a mark arrived without a usable source pointer, that is worth a reticle_session { action: "feedback" } with kind: "gap".
© reticlehq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/fix-what-i-pointed-at of reticlehq/reticle.
Open the folder on GitHubat commit 178e5c0
Fix What I Pointed At 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 |
|---|---|---|---|---|---|---|
| Fix What I Pointed At this skillreticlehq/reticle | 1.2k | — | ~878 | Automated safety check: Pass | Apache-2.0 | |
| Codewhale Dogfood Installcodewhale-hq/Codewhale | 41k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Issue Fixmono/SkiaSharp | 5.6k | — | ~5.1k | Automated safety check: Pass | MIT | |
| OpenROAD Issue TriageThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~842 | Automated safety check: Pass | BSD-3-Clause | |
| Pre-Merge Checkjsmastery-pro/skills | 1.5k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Fix The Classjoetawil7/first-pass | 98 | — | ~1.5k | Automated safety check: Pass | MIT |
codewhale-hq/Codewhale
Proves a Codewhale change in the real product: a stamped release build, an atomic local install, fresh-shell verification and manual QA that automated gates cannot cover.
mono/SkiaSharp
Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.
The-OpenROAD-Project/OpenROAD
Reproduces an OpenROAD GitHub bug from an attached tarball and shrinks the failing design with whittle.py so maintainers get a minimal test case.
jsmastery-pro/skills
A gate before merge: verify runs the real app against the spec, and review has a different model do a senior code review, without editing code.
joetawil7/first-pass
Bug-fix routine that fixes the whole class of bug, not just the reported instance.
supabase/supabase
Draft new or updated Supabase docs content for a feature or launch, grounded in product intent (Linear when available), a read of the actual code, and the docs style guide.
reticlehq/reticle
Applies red-green TDD to behavior unit tests cannot reach, by stating the expected outcome against the running app with Reticle before writing the feature.
reticlehq/reticle
Sweeps a running web app by clicking every reachable control, then reports dead buttons, console errors, failed requests and mismatches between API data and the screen.
reticlehq/reticle
Finds why a running web app misbehaves when the console is empty and the code looks fine, by reading the click, request, store and console together.
reticlehq/reticle
Drives and verifies Electron or Tauri desktop apps through Reticle, which sees the renderer and the IPC calls that a browser-based testing tool cannot observe.
reticlehq/reticle
Finds out why a passing test suite sits on top of a broken app by comparing what the running app does with what the tests claim, using Reticle.
reticlehq/reticle
Saves a user journey driven through the app as a deterministic regression check that replays with no model and no test code, using Reticle.
Categories
Picks up bugs a person flagged by pointing at elements in the running app, each mark carrying the element, their note and the source file and line, then fixes and verifies them. Reticle's running app has a Flag a bug control: a person clicks it, points at an element and types what is wrong. Each flag becomes a mark that carries the element, the note and a file and line pointer, so the usual cycle of screenshot, description and clarifying questions collapses into one call.
Fix What I Pointed At fits situations like: fixing bugs a designer or PM flagged directly in the running app; starting a session on an app someone has been clicking through; resolving a vague report like that button there without knowing the file.
Run `npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a claude-code`. Or copy the skill folder (skills/fix-what-i-pointed-at in reticlehq/reticle) into .claude/skills/fix-what-i-pointed-at in your project. Claude Code loads it when a task matches its description.
Run `npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a codex`. Or copy the skill folder (skills/fix-what-i-pointed-at in reticlehq/reticle) into .agents/skills/fix-what-i-pointed-at in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-what-i-pointed-at, .gemini/skills/fix-what-i-pointed-at, .github/skills/fix-what-i-pointed-at and .opencode/skills/fix-what-i-pointed-at in your project.
Going by SKILL.md and its folder, Fix What I Pointed At needs the command-line tools its instructions call (npx and curl). Our summary lists: The Reticle server and a running app, installed with npx @reticlehq/server init.
SKILL.md names 1 domain. In commands or code: docs.reticle.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Fix What I Pointed At is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 878 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Fix What I Pointed At: Codewhale Dogfood Install (codewhale-hq/Codewhale, 41k stars), Issue Fix (mono/SkiaSharp, 5.6k stars), OpenROAD Issue Triage (The-OpenROAD-Project/OpenROAD, 3.2k stars) and Pre-Merge Check (jsmastery-pro/skills, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
reticlehq (a GitHub organization) maintains it in reticlehq/reticle, which has 1,199 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 9, 2026.
Source: reticlehq/reticle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.