Agent skill

Explain Open

by haacked in haacked/dotfiles

Explain each open or skipped code-review item in plain English, weigh what happens on each side of the decision, and give a recommendation.

No licenceAuto-check passedDevelopment

Install Explain Open

skills CLI
$ npx skills add haacked/dotfiles --skill explain-open -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install haacked/dotfiles explain-open --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/haacked/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ai/skills/explain-open .claude/skills/explain-open && rm -rf skills-src

Use ~/.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/

Facts

Skill name
explain-open
GitHub stars
134
Token cost
~1.7k tokens
SKILL.md length
912 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
None found

At a glance

Explain each open or skipped code-review item in plain English, weigh what happens on each side of the decision, and give a recommendation.

  • Works in 3 steps: Gather the Open and Skipped Items → Explain Each Item → Summarize
  • Tasks that involve Code review
  • SKILL.md covers Step 1: Gather the Open and…, Step 2: Explain Each Item and Step 3: Summarize
  • Calls git; reaches github.com

What it does

Explain Open is an agent skill from haacked/dotfiles. Explain each open or skipped code-review item in plain English, weigh what happens on each side of the decision, and give a recommendation.

Its SKILL.md is about 1.7k 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, covering Code review and Plain language and style rules. The repository describes itself as: My dotfiles and scripts I use on dev machines.

When your agent uses it

  • Tasks that involve Code review
  • Tasks that involve Plain language and style rules

Example prompts

  • “/explain-open”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Gather the Open and Skipped Items
  2. Explain Each Item
  3. Summarize

What it can do on your machine

Read from SKILL.md and the folder at commit 23ffed9. 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:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

Explain Open loads about 1.7k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 912 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 912 words (~1,736 tokens).

“Code reviews leave two kinds of loose ends: items explicitly flagged as open questions for you to decide, and items a fix pass declined to act on. Instead of re-reading the raw finding and puzzling out what it actually means…”

— opening of SKILL.md by haacked
name
explain-open
argument-hint
[<pr-url>|<pr-number>|<branch>|<file>]
model
sonnet
metadata.execution-tier
balanced

Read the full SKILL.md on GitHub

Files

Just SKILL.md in ai/skills/explain-open of haacked/dotfiles.

Open the folder on GitHubat commit 23ffed9

Compare with similar skills

Explain Open 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.

Explain Open compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Explain Open this skillhaacked/dotfiles134—~1.7kAutomated safety check: PassNone
Cyclomatic Complexitysaurabhkumar8112/cyclomatic-complexity-skill405—~761Automated safety check: PassApache-2.0
Software Design Philosophyluoling8192/software-design-philosophy-skill346—~3.4kAutomated safety check: PassMIT
Code Reviewhardness1020/Leeway116—~301Automated safety check: PassMIT
Copilot Code Coachtimothywarner/chatgptclass143—~1.9kAutomated safety check: PassCustom licence
Code Reviewjohnku2011/boilerplates-with-ai-skills240—~708Automated safety check: PassMIT

Similar skills

  • Cyclomatic Complexity

    saurabhkumar8112/cyclomatic-complexity-skill

    Refactor code to reduce cyclomatic complexity so it stays readable, maintainable, and aligned with the long-term vision of the codebase, not just optimized for AI comprehension.

    405 GitHub stars~761 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Software Design Philosophy

    luoling8192/software-design-philosophy-skill

    Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition…

    346 GitHub stars~3.4k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Code Review

    hardness1020/Leeway

    Code quality review — identify patterns, anti-patterns, and improvements.

    116 GitHub stars~301 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Copilot Code Coach

    timothywarner/chatgptclass

    Socratic coding tutor powered by GitHub Copilot. An agent skill from timothywarner/chatgptclass.

    143 GitHub stars~1.9k tokensUpdated 18 days ago
    DevelopmentAuto-check passed
  • Code Review

    johnku2011/boilerplates-with-ai-skills

    A skill your agent uses when reviewing a diff or pull request — check correctness, tests, readability, security, and server/client boundaries before approving.

    240 GitHub stars~708 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Code Review And Quality

    HangYu8123/mini-harness

    Multi-axis, review-only code review of a diff across six axes — request achievement, correctness, readability/simplicity, architecture, security, and performance — with severity-labelled findings.

    199 GitHub stars~1.8k tokensUpdated 15 days ago
    DevelopmentAuto-check passed

More from haacked/dotfiles

All 29 skills in this repo
  • Support

    haacked/dotfiles

    Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.

    134 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Analyze Permissions

    haacked/dotfiles

    Analyze accumulated permissions and suggest smart wildcard patterns.

    134 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Followup

    haacked/dotfiles

    Capture a follow-up item mid-session in seconds, list open items, close one, or run a review pass.

    134 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Handoff

    haacked/dotfiles

    Write or resume a handoff document so the next agent session can pick up the current work.

    134 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Note

    haacked/dotfiles

    Capture complex technical discoveries into structured, reusable notes.

    134 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Quarterly Planning

    haacked/dotfiles

    Draft quarterly goals for a PostHog team (defaults to Feature Flags), clustering open issues into themes and producing goals in PostHog's HOGS format.

    134 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Explain Open

What does Explain Open do?

Explain each open or skipped code-review item in plain English, weigh what happens on each side of the decision, and give a recommendation. Explain Open is an agent skill from haacked/dotfiles. Explain each open or skipped code-review item in plain English, weigh what happens on each side of the decision, and give a recommendation.

When should I use Explain Open?

Explain Open fits situations like: tasks that involve Code review; tasks that involve Plain language and style rules.

How do I install Explain Open in Claude Code?

Run `npx skills add haacked/dotfiles --skill explain-open -a claude-code`. Or copy the skill folder (ai/skills/explain-open in haacked/dotfiles) into .claude/skills/explain-open in your project. Claude Code loads it when a task matches its description.

How do I install Explain Open in Codex?

Run `npx skills add haacked/dotfiles --skill explain-open -a codex`. Or copy the skill folder (ai/skills/explain-open in haacked/dotfiles) into .agents/skills/explain-open in your project. Codex loads it when a task matches its description.

Can I use Explain Open 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 haacked/dotfiles --skill explain-open -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explain-open, .gemini/skills/explain-open, .github/skills/explain-open and .opencode/skills/explain-open in your project.

What does Explain Open need to run?

Going by SKILL.md and its folder, Explain Open needs the command-line tools its instructions call (git).

Does Explain Open access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Explain Open 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 Explain Open use?

No licence was found for Explain Open or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Explain Open use?

About 1.7k tokens (SKILL.md is roughly 6.9k 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 Explain Open?

Skills that share tags, products or a category with Explain Open: Cyclomatic Complexity (saurabhkumar8112/cyclomatic-complexity-skill, 405 stars), Software Design Philosophy (luoling8192/software-design-philosophy-skill, 346 stars), Code Review (hardness1020/Leeway, 116 stars) and Copilot Code Coach (timothywarner/chatgptclass, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Explain Open?

haacked (a GitHub user) maintains it in haacked/dotfiles, which has 134 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.

Source: haacked/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.