PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Build and run iccDEV tool lanes under Memcheck, Helgrind, DRD, Massif, or Callgrind while preserving analyzer evidence.
Install Valgrind Analysis
$ npx skills add InternationalColorConsortium/iccDEV --skill valgrind-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install InternationalColorConsortium/iccDEV valgrind-analysis --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/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/valgrind-analysis .claude/skills/valgrind-analysis && 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 "valgrind-analysis" agent skill from https://github.com/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysis into .claude/skills/valgrind-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "valgrind-analysis", 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/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysisType 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 InternationalColorConsortium/iccDEV --skill valgrind-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install InternationalColorConsortium/iccDEV valgrind-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/valgrind-analysis .agents/skills/valgrind-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "valgrind-analysis" agent skill from https://github.com/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysis into .agents/skills/valgrind-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "valgrind-analysis", 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 InternationalColorConsortium/iccDEV --skill valgrind-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install InternationalColorConsortium/iccDEV valgrind-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/valgrind-analysis .cursor/skills/valgrind-analysis && 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 "valgrind-analysis" agent skill from https://github.com/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysis into .cursor/skills/valgrind-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "valgrind-analysis", 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/InternationalColorConsortium/iccDEV.git --path .github/skills/valgrind-analysis--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 InternationalColorConsortium/iccDEV --skill valgrind-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install InternationalColorConsortium/iccDEV valgrind-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/valgrind-analysis .gemini/skills/valgrind-analysis && 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 "valgrind-analysis" agent skill from https://github.com/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysis into .gemini/skills/valgrind-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "valgrind-analysis", 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 InternationalColorConsortium/iccDEV valgrind-analysisInstalls 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 InternationalColorConsortium/iccDEV --skill valgrind-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/valgrind-analysis .github/skills/valgrind-analysis && 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 "valgrind-analysis" agent skill from https://github.com/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysis into .github/skills/valgrind-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "valgrind-analysis", 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 InternationalColorConsortium/iccDEV --skill valgrind-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install InternationalColorConsortium/iccDEV valgrind-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InternationalColorConsortium/iccDEV.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/valgrind-analysis .opencode/skills/valgrind-analysis && 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 "valgrind-analysis" agent skill from https://github.com/InternationalColorConsortium/iccDEV/tree/master/.github/skills/valgrind-analysis into .opencode/skills/valgrind-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "valgrind-analysis", 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.
Facts
- Skill name
valgrind-analysis- GitHub stars
- 183
- Token cost
- ~636 tokens
- SKILL.md length
- 261 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Build and run iccDEV tool lanes under Memcheck, Helgrind, DRD, Massif, or Callgrind while preserving analyzer evidence.
- Works in 12 steps: Read ../../../docs/valgrind-analysis.md. → Select the smallest registered target… → Run .github/ci/valgrind/build.sh… → …
- Development work in your project
- SKILL.md covers Workflow, Container path and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Valgrind Analysis is an agent skill from InternationalColorConsortium/iccDEV. Build and run iccDEV tool lanes under Memcheck, Helgrind, DRD, Massif, or Callgrind while preserving analyzer evidence.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with GitHub. The repository describes itself as: iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of ICC color management profiles. The licence is BSD-3-Clause.
When your agent uses it
- Development work in your project
Example prompts
- “/valgrind-analysis”
Requirements
- Docker
- Pre-approved tools (allowed-tools): bash, read, grep, glob, shell(git:*), shell(docker:*)
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Read ../../../docs/valgrind-analysis.md.
- Select the smallest registered target that reaches the affected path.
- Run .github/ci/valgrind/build.sh --target TARGET to produce a separate
- Confirm the build rejects cached sanitizer flags and sanitizer-instrumented
- For runner or image QA, run .github/ci/valgrind/self-test.sh after building
- Run .github/ci/valgrind/run.sh --tool TOOL TARGET with a bounded timeout.
- Preserve the generated summary.tsv, analyzer log, stdout, stderr, and
- For concurrency, compare Helgrind and DRD rather than treating either as a
- For issue #2592 or m_jobReady notification changes, run
- Attribute findings to stack frames and observed synchronization behavior,
- For .icc corpus sweeps, build pawg or dump and use corpus.sh; do not
- Report the exact source revision, command, exit code, error count, and
What it can do on your machine
Read from SKILL.md and the folder at commit 3c2425d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
bashreadgrepglobshell(git:*)shell(docker:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Valgrind Analysis loads about 636 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 261 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from InternationalColorConsortium/iccDEV at commit 3c2425d, republished under its BSD-3-Clause licence (© InternationalColorConsortium). 261 words, ~636 tokens.
Download SKILL.mdSave it as
.claude/skills/valgrind-analysis/SKILL.md (or your agent's skills folder).- name
- valgrind-analysis
- description
- Build and run iccDEV tool lanes under Memcheck, Helgrind, DRD, Massif, or Callgrind while preserving analyzer evidence.
- allowed-tools
- bash, read, grep, glob, shell(git:*), shell(docker:*)
Valgrind Analysis
Use this skill for uninitialized-memory, invalid-access, leak, synchronization, heap-growth, or call-profile investigations against iccDEV tools.
Workflow
- Read
../../../docs/valgrind-analysis.md. - Select the smallest registered target that reaches the affected path.
- Run
.github/ci/valgrind/build.sh --target TARGETto produce a separate non-sanitized Debug build. - Confirm the build rejects cached sanitizer flags and sanitizer-instrumented binaries, including statically linked runtimes.
- For runner or image QA, run
.github/ci/valgrind/self-test.shafter building thedumptarget. - Run
.github/ci/valgrind/run.sh --tool TOOL TARGETwith a bounded timeout. - Preserve the generated
summary.tsv, analyzer log, stdout, stderr, and generated work files. - For concurrency, compare Helgrind and DRD rather than treating either as a substitute for TSan.
- For issue #2592 or
m_jobReadynotification changes, run.github/ci/valgrind/issue-2592-regression.sh; require both analyzers to be clean and their generated TIFFs to match. - Attribute findings to stack frames and observed synchronization behavior, not input filenames.
- For
.icccorpus sweeps, buildpawgordumpand usecorpus.sh; do not use word-splitting command substitution aroundfind. - Report the exact source revision, command, exit code, error count, and evidence directory.
Use --allow-findings only when collecting a known or deliberately compared
finding. Never use it to turn an unexplained result into a clean gate.
Container path
The unified image exposes iccdev-valgrind-build, iccdev-valgrind-run,
iccdev-valgrind-status, iccdev-valgrind-validate, and
iccdev-valgrind-self-test. These commands write to /workspace/valgrind by
default and must not wrap /workspace/build.
The repository's .github/ci/valgrind/corpus.sh supports mounted corpus paths
inside the unified image. Preserve per-profile evidence outside the container;
prefer tar streaming when a writable bind mount has a different owner.
References
../../../docs/valgrind-analysis.md../../prompts/valgrind-analysis.prompt.md../sanitizer-repro/SKILL.md../regression-container-maintainer/SKILL.md
© InternationalColorConsortium, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/valgrind-analysis of InternationalColorConsortium/iccDEV.
Open the folder on GitHubat commit 3c2425d
Compare with similar skills
Valgrind Analysis 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 |
|---|---|---|---|---|---|---|
| Valgrind Analysis this skillInternationalColorConsortium/iccDEV | 183 | — | ~636 | Automated safety check: Pass | BSD-3-Clause | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
More from InternationalColorConsortium/iccDEV
All 23 skills in this repoAfl Smoke
InternationalColorConsortium/iccDEV
Run or update the iccDEV AFL++ manual smoke workflow, seeds, and maintainer documentation.
Avx2 Clut Diagnostics
InternationalColorConsortium/iccDEV
Diagnose runtime-dispatched AVX2 3D CLUT interpolation, collect trace evidence, validate vector and masked-tail output, and prepare optimization handoff data.
Clusterfuzzlite
InternationalColorConsortium/iccDEV
Build, test, or update the iccDEV ClusterFuzzLite libFuzzer integration across ASan, UBSan, and MSan.
iOS Clut Editor
InternationalColorConsortium/iccDEV
Build, review, and maintain the ios-clut-editor profile and 3D CLUT editing proof-of-concept app without repeating prior iOS review-loop failures.
iOS Manual Examples
InternationalColorConsortium/iccDEV
Maintain the manual iOS example app CMake projects, local Xcode build helpers, device signing guard rails, and documentation.
JSON Config Regression
InternationalColorConsortium/iccDEV
Validate iccDEV JSON/profile config parser changes with fail-closed regression gates and CLI exercises.
Related
Works with
Categories
Questions about Valgrind Analysis
What does Valgrind Analysis do?
Build and run iccDEV tool lanes under Memcheck, Helgrind, DRD, Massif, or Callgrind while preserving analyzer evidence. Valgrind Analysis is an agent skill from InternationalColorConsortium/iccDEV. Build and run iccDEV tool lanes under Memcheck, Helgrind, DRD, Massif, or Callgrind while preserving analyzer evidence.
When should I use Valgrind Analysis?
Valgrind Analysis fits situations like: development work in your project.
How do I install Valgrind Analysis in Claude Code?
Run `npx skills add InternationalColorConsortium/iccDEV --skill valgrind-analysis -a claude-code`. Or copy the skill folder (.github/skills/valgrind-analysis in InternationalColorConsortium/iccDEV) into .claude/skills/valgrind-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Valgrind Analysis in Codex?
Run `npx skills add InternationalColorConsortium/iccDEV --skill valgrind-analysis -a codex`. Or copy the skill folder (.github/skills/valgrind-analysis in InternationalColorConsortium/iccDEV) into .agents/skills/valgrind-analysis in your project. Codex loads it when a task matches its description.
Can I use Valgrind Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add InternationalColorConsortium/iccDEV --skill valgrind-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/valgrind-analysis, .gemini/skills/valgrind-analysis, .github/skills/valgrind-analysis and .opencode/skills/valgrind-analysis in your project.
What does Valgrind Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Valgrind Analysis is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: bash, read, grep, glob, shell(git:*), shell(docker:*).
Does Valgrind Analysis access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Valgrind Analysis safe to install?
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.
What licence does Valgrind Analysis use?
Valgrind Analysis is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Valgrind Analysis use?
About 636 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Valgrind Analysis?
Skills that share tags, products or a category with Valgrind Analysis: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Valgrind Analysis?
InternationalColorConsortium (a GitHub organization) maintains it in InternationalColorConsortium/iccDEV, which has 183 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 9, 2026.
Source: InternationalColorConsortium/iccDEV on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.