Roo Conflict Resolution
zgsm-ai/costrict
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.
Find all hardcoded path-to-editor-name mappings in the CLI (cli/src/analysis.ts::getEditorSourceFromPath) and VS Code extension (src/workspaceHelpers.ts::getEditorTypeFromPath), verify they return…
Install Validate Editor Names
$ npx skills add rajbos/ai-engineering-fluency --skill validate-editor-names -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rajbos/ai-engineering-fluency validate-editor-names --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/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/validate-editor-names .claude/skills/validate-editor-names && 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 "validate-editor-names" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-names into .claude/skills/validate-editor-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-editor-names", 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/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-namesType 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 rajbos/ai-engineering-fluency --skill validate-editor-names -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rajbos/ai-engineering-fluency validate-editor-names --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/validate-editor-names .agents/skills/validate-editor-names && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validate-editor-names" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-names into .agents/skills/validate-editor-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-editor-names", 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 rajbos/ai-engineering-fluency --skill validate-editor-names -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rajbos/ai-engineering-fluency validate-editor-names --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/validate-editor-names .cursor/skills/validate-editor-names && 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 "validate-editor-names" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-names into .cursor/skills/validate-editor-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-editor-names", 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/rajbos/ai-engineering-fluency.git --path .claude/skills/validate-editor-names--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 rajbos/ai-engineering-fluency --skill validate-editor-names -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rajbos/ai-engineering-fluency validate-editor-names --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/validate-editor-names .gemini/skills/validate-editor-names && 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 "validate-editor-names" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-names into .gemini/skills/validate-editor-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-editor-names", 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 rajbos/ai-engineering-fluency validate-editor-namesInstalls 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 rajbos/ai-engineering-fluency --skill validate-editor-names -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/validate-editor-names .github/skills/validate-editor-names && 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 "validate-editor-names" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-names into .github/skills/validate-editor-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-editor-names", 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 rajbos/ai-engineering-fluency --skill validate-editor-names -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rajbos/ai-engineering-fluency validate-editor-names --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/validate-editor-names .opencode/skills/validate-editor-names && 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 "validate-editor-names" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/validate-editor-names into .opencode/skills/validate-editor-names/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-editor-names", 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
validate-editor-names- GitHub stars
- 116
- Token cost
- ~1.1k tokens
- SKILL.md length
- 440 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Find all hardcoded path-to-editor-name mappings in the CLI (cli/src/analysis.ts::getEditorSourceFromPath) and VS Code extension (src/workspaceHelpers.ts::getEditorTypeFromPath), verify they return…
- Works in 4 steps: CLI-only coverage — every unique name… → VS Code-only coverage — every unique… → Cross-function consistency — for a… → …
- Development work in your project
- SKILL.md covers What the script checks, Usage, When to run this skill and How to fix failures, plus 1 more section
- Calls node
What it does
Validate Editor Names is an agent skill from rajbos/ai-engineering-fluency. Find all hardcoded path-to-editor-name mappings in the CLI (cli/src/analysis.ts::getEditorSourceFromPath) and VS Code extension (src/workspaceHelpers.ts::getEditorTypeFromPath), verify they return matching friendly display names for the same path patterns, and confirm every CLI-returned name appears in the EDITORICONMAP in formatUtils.ts. Use after adding a new editor adapter, after CLI changes, or if JetBrains/other CLI-based consumers show raw editor keys instead of friendly names.
Its SKILL.md is about 1.1k 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 Visual Studio Code and JetBrains IDEs. The repository describes itself as: Extension that shows information about the estimated token usage and more of AI in editors/CLI's. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/validate-editor-names”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- CLI-only coverage — every unique name returned by
- VS Code-only coverage — every unique name returned by
- Cross-function consistency — for a canonical set of test paths the CLI
- Ordering invariants — warns if a broad path pattern (e.g. /.copilot/)
What it can do on your machine
Read from SKILL.md and the folder at commit 64b51e6. 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:
node
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
Validate Editor Names loads about 1.1k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 440 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 rajbos/ai-engineering-fluency at commit 64b51e6, republished under its MIT licence (© rajbos). 440 words, ~1,146 tokens.
Download SKILL.mdSave it as
.claude/skills/validate-editor-names/SKILL.md (or your agent's skills folder).- name
- validate-editor-names
- description
- Find all hardcoded path-to-editor-name mappings in the CLI (cli/src/analysis.ts::getEditorSourceFromPath) and VS Code extension (src/workspaceHelpers.ts::getEditorTypeFromPath), verify they return matching friendly display names for the same path patterns, and confirm every CLI-returned name appears in the EDITOR_ICON_MAP in formatUtils.ts. Use after adding a new editor adapter, after CLI changes, or if JetBrains/other CLI-based consumers show raw editor keys instead of friendly names.
Validate Editor Names Skill
Checks that the CLI and the VS Code extension always agree on editor display names, and that every name has an icon in the webview icon map.
There are three sources of truth that must stay in sync:
| Source | File | Function / symbol |
|---|---|---|
| CLI path detector | cli/src/analysis.ts | getEditorSourceFromPath |
| VS Code path detector | src/workspaceHelpers.ts | getEditorTypeFromPath (delegates to detectToolEditorFromPath + detectVSCodeVariantFromPath) |
| Webview icon map | vscode-extension/src/webview/shared/formatUtils.ts | EDITOR_ICON_MAP + EditorName union type |
The JetBrains plugin (and any future CLI-based consumer) gets its editor names
exclusively from the CLI via CliBridge.kt. If the CLI returns a raw
lowercase key instead of a friendly display name the UI falls back to the raw
key everywhere: chart labels, the session list, the stats command.
What the script checks
- CLI-only coverage — every unique name returned by
getEditorSourceFromPathexists inEDITOR_ICON_MAP. - VS Code-only coverage — every unique name returned by
getEditorTypeFromPathexists inEDITOR_ICON_MAP. - Cross-function consistency — for a canonical set of test paths the CLI and VS Code detectors return identical names. Any mismatch is a bug.
- Ordering invariants — warns if a broad path pattern (e.g.
/.copilot/) appears before a more specific one (e.g./.copilot/jb/) in the CLI function, which would cause the broad check to shadow the specific one.
Usage
# Run all checks and print a human-readable report
node .github/skills/validate-editor-names/validate-editor-names.js
# Machine-readable JSON (for CI / further processing)
node .github/skills/validate-editor-names/validate-editor-names.js --json
# Show help
node .github/skills/validate-editor-names/validate-editor-names.js --helpOptions
| Flag | Meaning |
|---|---|
--json | Emit JSON only (no ANSI colour) |
--help | Usage |
Exit codes
0— all checks pass1— one or more checks failed (missing icon, name mismatch, ordering issue)2— configuration / environment error (source files not found)
Show full SKILL.md (196 more words)Show less
When to run this skill
- After adding a new editor adapter (
src/adapters/) - After modifying
getEditorSourceFromPathorgetEditorTypeFromPath - After updating
EDITOR_ICON_MAPinformatUtils.ts - When JetBrains (or another CLI-based view) shows raw editor keys instead of friendly names — this skill will pinpoint which path pattern is missing or mismatched
How to fix failures
| Failure type | Likely cause | Fix |
|---|---|---|
| Missing icon for CLI name | New editor added to CLI but not to formatUtils.ts | Add entry to EditorName union and EDITOR_ICON_MAP |
| Missing icon for VS Code name | New editor added to VS Code adapter but not to formatUtils.ts | Same as above |
| Name mismatch for a test path | CLI returns raw key; VS Code returns friendly name (or vice versa) | Align getEditorSourceFromPath to match getEditorTypeFromPath |
| Ordering issue | Broad includes check appears before specific one in CLI function | Reorder checks in getEditorSourceFromPath so specific paths come first |
Related files
cli/src/analysis.ts—getEditorSourceFromPath(the CLI implementation)src/workspaceHelpers.ts—getEditorTypeFromPath,detectToolEditorFromPath,detectVSCodeVariantFromPathvscode-extension/src/webview/shared/formatUtils.ts—EditorNametype +EDITOR_ICON_MAPjetbrains-plugin/src/main/kotlin/.../CliBridge.kt— the JetBrains host that calls the CLI binary and feeds the returned editor names straight into the shared webview bundle.github/skills/validate-session-schemas/— validates session file schemas (a complementary skill; run both when adding a new adapter)docs/logFilesSchema/— per-platform schema documentation
© rajbos, MIT. 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 .claude/skills/validate-editor-names of rajbos/ai-engineering-fluency.
Open the folder on GitHubat commit 64b51e6
Compare with similar skills
Validate Editor Names 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 |
|---|---|---|---|---|---|---|
| Validate Editor Names this skillrajbos/ai-engineering-fluency | 116 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Roo Conflict Resolutionzgsm-ai/costrict | 4.4k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Evals Contextzgsm-ai/costrict | 4.4k | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Debug Surefireeclipse-rdf4j/rdf4j | 420 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause | |
| Claude Docs Consultantcentminmod/my-claude-code-setup | 2.7k | — | ~959 | Automated safety check: Pass | MIT | |
| Doc SyncJetBrains/ideavim | 10k | 2 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Evals Context
zgsm-ai/costrict
Provides context about the CoStrict evals system structure in this monorepo.
Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
Claude Docs Consultant
centminmod/my-claude-code-setup
Consult official Claude Code documentation from code.claude.com using selective fetching.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
- Official
Changelog
JetBrains/ideavim
Maintains the IdeaVim changelog (CHANGES.md). An agent skill from JetBrains/ideavim.
More from rajbos/ai-engineering-fluency
All 21 skills in this repoCheck Urls
rajbos/ai-engineering-fluency
Find all hardcoded URLs in TypeScript source files and verify they resolve (return HTTP 2xx/3xx).
Create Issue
rajbos/ai-engineering-fluency
Create a well-scoped GitHub issue in this repo. An agent skill from rajbos/ai-engineering-fluency.
Deduplicate Code
rajbos/ai-engineering-fluency
Detect copy-pasted code blocks across the shared source (vscode-extension/src, the repo-root src/, cli/src) with the dependency-free check-code-duplication.js detector, then pick one duplicate group…
Improve Tool Families
rajbos/ai-engineering-fluency
Analyze coverage of the vscode-extension's tool-family definitions (DEFAULTTOOLFAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a…
Load Cache Data
rajbos/ai-engineering-fluency
Load and display the last 10 cache entries as raw JSON output.
PR Risk Review
rajbos/ai-engineering-fluency
Assess the risk of a changeset (a PR, a branch, or the working tree) and classify it as low, medium, or high with a written rationale.
Related
Works with
Categories
Questions about Validate Editor Names
What does Validate Editor Names do?
Find all hardcoded path-to-editor-name mappings in the CLI (cli/src/analysis.ts::getEditorSourceFromPath) and VS Code extension (src/workspaceHelpers.ts::getEditorTypeFromPath), verify they return…. Validate Editor Names is an agent skill from rajbos/ai-engineering-fluency.ts.
When should I use Validate Editor Names?
Validate Editor Names fits situations like: development work in your project.
How do I install Validate Editor Names in Claude Code?
Run `npx skills add rajbos/ai-engineering-fluency --skill validate-editor-names -a claude-code`. Or copy the skill folder (.claude/skills/validate-editor-names in rajbos/ai-engineering-fluency) into .claude/skills/validate-editor-names in your project. Claude Code loads it when a task matches its description.
How do I install Validate Editor Names in Codex?
Run `npx skills add rajbos/ai-engineering-fluency --skill validate-editor-names -a codex`. Or copy the skill folder (.claude/skills/validate-editor-names in rajbos/ai-engineering-fluency) into .agents/skills/validate-editor-names in your project. Codex loads it when a task matches its description.
Can I use Validate Editor Names 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 rajbos/ai-engineering-fluency --skill validate-editor-names -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-editor-names, .gemini/skills/validate-editor-names, .github/skills/validate-editor-names and .opencode/skills/validate-editor-names in your project.
What does Validate Editor Names need to run?
Going by SKILL.md and its folder, Validate Editor Names needs the command-line tools its instructions call (node).
Does Validate Editor Names 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 Validate Editor Names 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 Validate Editor Names use?
Validate Editor Names is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Validate Editor Names use?
About 1.1k tokens (SKILL.md is roughly 4.6k 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 Validate Editor Names?
Skills that share tags, products or a category with Validate Editor Names: Roo Conflict Resolution (zgsm-ai/costrict, 4.4k stars), Evals Context (zgsm-ai/costrict, 4.4k stars), Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars) and Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Validate Editor Names?
rajbos (a GitHub user) maintains it in rajbos/ai-engineering-fluency, which has 116 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.
Source: rajbos/ai-engineering-fluency on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.