Observe Trace
ruvnet/ruflo
Trace agent execution by collecting spans and building a trace tree for a task
Writes and reviews Iris compiler comments, algorithm traces, and documentation examples.
Custom licenceAuto-check passed
Install Writing Code Commentary
$ npx skills add purefunctor/purescript-iris --skill writing-code-commentary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install purefunctor/purescript-iris writing-code-commentary --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/purefunctor/purescript-iris.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-code-commentary .claude/skills/writing-code-commentary && 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 "writing-code-commentary" agent skill from https://github.com/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentary into .claude/skills/writing-code-commentary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-code-commentary", 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/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentaryType 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 purefunctor/purescript-iris --skill writing-code-commentary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install purefunctor/purescript-iris writing-code-commentary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/purefunctor/purescript-iris.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-code-commentary .agents/skills/writing-code-commentary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-code-commentary" agent skill from https://github.com/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentary into .agents/skills/writing-code-commentary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-code-commentary", 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 purefunctor/purescript-iris --skill writing-code-commentary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install purefunctor/purescript-iris writing-code-commentary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/purefunctor/purescript-iris.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-code-commentary .cursor/skills/writing-code-commentary && 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 "writing-code-commentary" agent skill from https://github.com/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentary into .cursor/skills/writing-code-commentary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-code-commentary", 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/purefunctor/purescript-iris.git --path .agents/skills/writing-code-commentary--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 purefunctor/purescript-iris --skill writing-code-commentary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install purefunctor/purescript-iris writing-code-commentary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/purefunctor/purescript-iris.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-code-commentary .gemini/skills/writing-code-commentary && 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 "writing-code-commentary" agent skill from https://github.com/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentary into .gemini/skills/writing-code-commentary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-code-commentary", 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 purefunctor/purescript-iris writing-code-commentaryInstalls 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 purefunctor/purescript-iris --skill writing-code-commentary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/purefunctor/purescript-iris.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-code-commentary .github/skills/writing-code-commentary && 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 "writing-code-commentary" agent skill from https://github.com/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentary into .github/skills/writing-code-commentary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-code-commentary", 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 purefunctor/purescript-iris --skill writing-code-commentary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install purefunctor/purescript-iris writing-code-commentary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/purefunctor/purescript-iris.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-code-commentary .opencode/skills/writing-code-commentary && 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 "writing-code-commentary" agent skill from https://github.com/purefunctor/purescript-iris/tree/main/.agents/skills/writing-code-commentary into .opencode/skills/writing-code-commentary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-code-commentary", 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
writing-code-commentary- GitHub stars
- 117
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,386 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Writes and reviews Iris compiler comments, algorithm traces, and documentation examples.
- Works in 4 steps: State one generalized rule → Introduce concrete source and target types → Trace examples beside the corresponding… → …
- Documenting non-obvious compiler transformations
- SKILL.md covers Establish the local style, Write from the goal, not from…, Structure staged algorithm… and Describe recursion by semantic…, plus 8 more sections
- Calls just, git and cargo
What it does
Writing Code Commentary is an agent skill from purefunctor/purescript-iris. Writes and reviews Iris compiler comments, algorithm traces, and documentation examples. Use when documenting non-obvious compiler transformations, revising inline commentary, or applying documentation-focused review nits.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A compiler for the PureScript programming language.
When your agent uses it
- Documenting non-obvious compiler transformations
- Revising inline commentary
- Applying documentation-focused review nits
Example prompts
- “Use the writing-code-commentary skill to write and reviews Iris compiler comments, algorithm traces, and documentation examples”
- “/writing-code-commentary”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- State one generalized rule
- Introduce concrete source and target types
- Trace examples beside the corresponding construction steps
- Complete every example in parallel
What it can do on your machine
Read from SKILL.md and the folder at commit f62075e. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
justgitcargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Writing Code Commentary loads about 2.8k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 1,386 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,386 words (~2,787 tokens).
“Make difficult compiler code reviewable without narrating code that already explains itself.”
- name
- writing-code-commentary
Files
Just SKILL.md in .agents/skills/writing-code-commentary of purefunctor/purescript-iris.
Open the folder on GitHubat commit f62075e
Compare with similar skills
Writing Code Commentary 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 |
|---|---|---|---|---|---|---|
| Writing Code Commentary this skillpurefunctor/purescript-iris | 117 | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Observe Traceruvnet/ruflo | 74k | — | ~522 | Automated safety check: Notes | MIT | |
| No Commentscursor/plugins | 10k | 7 repos | ~640 | Automated safety check: Pass | None | |
| Commentsanthropics/claude-for-legal | 9.6k | 1 repos | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Clean Up Commentsthedaviddias/Front-End-Checklist | 74k | — | ~435 | Automated safety check: Pass | MIT | |
| Comment Checkercode-yeongyu/oh-my-openagent | 70k | — | ~160 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
No Comments
cursor/plugins
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- Official
Comments
anthropics/claude-for-legal
Review open NPRM comment periods, log decisions, track deadlines.
Clean Up Comments
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production.
Comment Checker
code-yeongyu/oh-my-openagent
A skill your agent uses when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
- Official
Algorithmic Art with p5.js
anthropics/skills
Creates original generative art in two steps: a written algorithmic philosophy, then a p5.js sketch with seeded randomness and an interactive viewer for exploring parameters.
More from purefunctor/purescript-iris
All 8 skills in this repoRunning Compatibility Checks
purefunctor/purescript-iris
Runs Iris package-set compatibility comparisons with release-built verifiers.
Cutting Releases
purefunctor/purescript-iris
Cuts Iris GitHub releases through the version-bump PR, merge commit, tag-driven build workflow, attestations, installer tests, and generated release notes.
Stylex
purefunctor/purescript-iris
Write StyleX styles in PureScript with Iris through the built-in Iris.StyleX, Iris.StyleX.When, and Iris.StyleX.Types modules, which Iris compiles to @stylexjs/stylex calls.
Watch
purefunctor/purescript-iris
Ask a running iris watch about a PureScript project with iris watch query for signatures, module exports, definitions, references, instances, dependent modules, name search, diagnostics, and…
Workflow Integration Tests
purefunctor/purescript-iris
Workflow for adding and updating Iris integration-test fixtures for unified compiler, lowering, resolving, and LSP behavior.
Workflow Regression Tests
purefunctor/purescript-iris
Workflow for producing auditable Git or jj history for a known compiler bug fix.
Questions about Writing Code Commentary
What does Writing Code Commentary do?
Writes and reviews Iris compiler comments, algorithm traces, and documentation examples. Writing Code Commentary is an agent skill from purefunctor/purescript-iris. Writes and reviews Iris compiler comments, algorithm traces, and documentation examples.
When should I use Writing Code Commentary?
Writing Code Commentary fits situations like: documenting non-obvious compiler transformations; revising inline commentary; applying documentation-focused review nits.
How do I install Writing Code Commentary in Claude Code?
Run `npx skills add purefunctor/purescript-iris --skill writing-code-commentary -a claude-code`. Or copy the skill folder (.agents/skills/writing-code-commentary in purefunctor/purescript-iris) into .claude/skills/writing-code-commentary in your project. Claude Code loads it when a task matches its description.
How do I install Writing Code Commentary in Codex?
Run `npx skills add purefunctor/purescript-iris --skill writing-code-commentary -a codex`. Or copy the skill folder (.agents/skills/writing-code-commentary in purefunctor/purescript-iris) into .agents/skills/writing-code-commentary in your project. Codex loads it when a task matches its description.
Can I use Writing Code Commentary 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 purefunctor/purescript-iris --skill writing-code-commentary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-code-commentary, .gemini/skills/writing-code-commentary, .github/skills/writing-code-commentary and .opencode/skills/writing-code-commentary in your project.
What does Writing Code Commentary need to run?
Going by SKILL.md and its folder, Writing Code Commentary needs the command-line tools its instructions call (just, git and cargo).
Does Writing Code Commentary access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Writing Code Commentary 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 Writing Code Commentary use?
Writing Code Commentary has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Writing Code Commentary use?
About 2.8k tokens (SKILL.md is roughly 11k 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 Writing Code Commentary?
Skills that share tags, products or a category with Writing Code Commentary: Observe Trace (ruvnet/ruflo, 74k stars), No Comments (cursor/plugins, 10k stars), Comments (anthropics/claude-for-legal, 9.6k stars) and Clean Up Comments (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Code Commentary?
purefunctor (a GitHub user) maintains it in purefunctor/purescript-iris, which has 117 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 8, 2026.
Source: purefunctor/purescript-iris on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.