Address PR Feedback for ruby-git
ruby-git/ruby-git
Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…
Set up or audit Nate's standard dev environment in a project directory.
Install Dev Env Setup
$ npx skills add nateberkopec/dotfiles --skill dev-env-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nateberkopec/dotfiles dev-env-setup --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/nateberkopec/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/files/home/.claude/skills/dev-env-setup .claude/skills/dev-env-setup && 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 "dev-env-setup" agent skill from https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setup into .claude/skills/dev-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-env-setup", 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/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setupType 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 nateberkopec/dotfiles --skill dev-env-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nateberkopec/dotfiles dev-env-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nateberkopec/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/files/home/.claude/skills/dev-env-setup .agents/skills/dev-env-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dev-env-setup" agent skill from https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setup into .agents/skills/dev-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-env-setup", 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 nateberkopec/dotfiles --skill dev-env-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nateberkopec/dotfiles dev-env-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nateberkopec/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/files/home/.claude/skills/dev-env-setup .cursor/skills/dev-env-setup && 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 "dev-env-setup" agent skill from https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setup into .cursor/skills/dev-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-env-setup", 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/nateberkopec/dotfiles.git --path files/home/.claude/skills/dev-env-setup--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 nateberkopec/dotfiles --skill dev-env-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nateberkopec/dotfiles dev-env-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nateberkopec/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/files/home/.claude/skills/dev-env-setup .gemini/skills/dev-env-setup && 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 "dev-env-setup" agent skill from https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setup into .gemini/skills/dev-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-env-setup", 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 nateberkopec/dotfiles dev-env-setupInstalls 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 nateberkopec/dotfiles --skill dev-env-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nateberkopec/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/files/home/.claude/skills/dev-env-setup .github/skills/dev-env-setup && 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 "dev-env-setup" agent skill from https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setup into .github/skills/dev-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-env-setup", 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 nateberkopec/dotfiles --skill dev-env-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nateberkopec/dotfiles dev-env-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nateberkopec/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/files/home/.claude/skills/dev-env-setup .opencode/skills/dev-env-setup && 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 "dev-env-setup" agent skill from https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/dev-env-setup into .opencode/skills/dev-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-env-setup", 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
dev-env-setup- GitHub stars
- 146
- Token cost
- ~671 tokens
- SKILL.md length
- 289 words
- Files
- 26 (incl. scripts, references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Set up or audit Nate's standard dev environment in a project directory.
- Works in 6 steps: Establish ownership and a clean Git… → Run the checker and inspect the… → Load only the applicable references and… → …
- Standardized project tooling
- SKILL.md covers Safety and ownership, Choose references and Workflow
- Calls git
What it does
Dev Env Setup is an agent skill from nateberkopec/dotfiles. Set up or audit Nate's standard dev environment in a project directory. Use for mise tasks, hk hooks, CI hardening, or standardized project tooling.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 28 other files, including scripts and reference files (for example `references/hk-hooks.md`, `references/mise-and-hooks.md` and `references/project-commands.md`).
It sits in Development. It works with Git and Ruby. The repository describes itself as: yup we're doin the thing.
When your agent uses it
- Standardized project tooling
Example prompts
- “/dev-env-setup”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish ownership and a clean Git baseline.
- Run the checker and inspect the project’s existing toolchain.
- Load only the applicable references and make the smallest changes that satisfy failures.
- Run dependency preparation, then every standard task directly.
- Run the checker again.
- Confirm git status is clean for foreign repositories; for owned repositories, account for every intended tracked change.
What it can do on your machine
Read from SKILL.md and the folder at commit dbfc96a. 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
Ships 11 files in scripts/, which the agent can run.
Shell commands in SKILL.md call:
git
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
Dev Env Setup loads about 671 tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 41 tokens; SKILL.md has 289 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:20
fnox/1Password runtime references. Keep `.env` untracked and examples fake. GitHub Actions must pin third-party actions
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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 289 words (~671 tokens).
- name
- dev-env-setup
Files
SKILL.md and 25 other files (scripts, references) in files/home/.claude/skills/dev-env-setup of nateberkopec/dotfiles.
- SKILL.md
- references/hk-hooks.md
- references/mise-and-hooks.md
- references/project-commands.md
- references/ruby-projects.md
- references/security-and-ci.md
- references/standard-tasks.md
- scripts/check-dev-env.fish
- scripts/check-dev-env/context.fish
- scripts/check-dev-env/env.fish
- scripts/check-dev-env/git.fish
- scripts/check-dev-env/github-actions.fish
- scripts/check-dev-env/gitleaks-default.toml
- scripts/check-dev-env/hk-reporting.fish
- scripts/check-dev-env/hk.fish
- scripts/check-dev-env/mise-config.fish
- scripts/check-dev-env/mise-task-checks.fish
- scripts/check-dev-env/mise-tasks.fish
- … and 8 more
Open the folder on GitHubat commit dbfc96a
Compare with similar skills
Dev Env Setup 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 |
|---|---|---|---|---|---|---|
| Dev Env Setup this skillnateberkopec/dotfiles | 146 | — | ~671 | Automated safety check: Notes | None | |
| Address PR Feedback for ruby-gitruby-git/ruby-git | 1.8k | — | ~657 | Automated safety check: Pass | MIT | |
| Dgv1r3n/dinesh-gilfoyle | 195 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Breaking Change Analysisruby-git/ruby-git | 1.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Releasebibendi/schked | 138 | — | ~670 | Automated safety check: Notes | MIT | |
| Git Command Class Implementationruby-git/ruby-git | 1.8k | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Dg
v1r3n/dinesh-gilfoyle
A skill your agent uses when the user invokes /dg for an entertaining adversarial code review with Dinesh vs Gilfoyle banter from Silicon Valley
Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
Release
bibendi/schked
Guides through the full gem release process — bump version, update CHANGELOG, tag, push to RubyGems, and create GitHub Release.
Git Command Class Implementation
ruby-git/ruby-git
Scaffolds and reviews `Git::Commands::*` classes in the ruby-git library, with unit tests, integration tests and YARD docs, using the Base command architecture.
Gem Dependency Management
ruby-git/ruby-git
Workflow for updating gem dependencies and fixing CVEs in the ruby-git project: assess with bundle outdated and audit, edit the gemspec, test, then commit with conventional messages.
More from nateberkopec/dotfiles
Deep Research
nateberkopec/dotfiles
Produce an in-depth, source-grounded research report. An agent skill from nateberkopec/dotfiles.
Fix Upstream
nateberkopec/dotfiles
Reproduce, report, and work around bugs in upstream software managed by these dotfiles.
Handouts
nateberkopec/dotfiles
Compose and typeset polished PDFs for personal reading on paper.
Printing
nateberkopec/dotfiles
Print files or selected pages, check printer status, or troubleshoot printing problems.
Related
Categories
Questions about Dev Env Setup
What does Dev Env Setup do?
Set up or audit Nate's standard dev environment in a project directory. Dev Env Setup is an agent skill from nateberkopec/dotfiles. Set up or audit Nate's standard dev environment in a project directory.
When should I use Dev Env Setup?
Dev Env Setup fits situations like: standardized project tooling.
How do I install Dev Env Setup in Claude Code?
Run `npx skills add nateberkopec/dotfiles --skill dev-env-setup -a claude-code`. Or copy the skill folder (files/home/.claude/skills/dev-env-setup in nateberkopec/dotfiles) into .claude/skills/dev-env-setup in your project. Claude Code loads it when a task matches its description.
How do I install Dev Env Setup in Codex?
Run `npx skills add nateberkopec/dotfiles --skill dev-env-setup -a codex`. Or copy the skill folder (files/home/.claude/skills/dev-env-setup in nateberkopec/dotfiles) into .agents/skills/dev-env-setup in your project. Codex loads it when a task matches its description.
Can I use Dev Env Setup 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 nateberkopec/dotfiles --skill dev-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-env-setup, .gemini/skills/dev-env-setup, .github/skills/dev-env-setup and .opencode/skills/dev-env-setup in your project.
What does Dev Env Setup need to run?
Going by SKILL.md and its folder, Dev Env Setup needs the command-line tools its instructions call (git).
Does Dev Env Setup 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 Dev Env Setup safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Dev Env Setup use?
No licence was found for Dev Env Setup or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Dev Env Setup use?
About 671 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.
What are the alternatives to Dev Env Setup?
Skills that share tags, products or a category with Dev Env Setup: Address PR Feedback for ruby-git (ruby-git/ruby-git, 1.8k stars), Dg (v1r3n/dinesh-gilfoyle, 195 stars), Breaking Change Analysis (ruby-git/ruby-git, 1.8k stars) and Release (bibendi/schked, 138 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dev Env Setup?
nateberkopec (a GitHub user) maintains it in nateberkopec/dotfiles, which has 146 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: nateberkopec/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.