dotfiles

Original：🇺🇸 English

Translated

Use when working with the bmthd/dotfiles setup — either changing the repository itself (mise tools, install.sh, docs, the skills that live there) and opening a PR, or applying an available update to THIS machine after the shell printed "dotfiles の更新があります". Invoke as /dotfiles pr <change> or /dotfiles apply.

2installs

Sourcebmthd/dotfiles

Added on2026-08-30

NPX Install

npx skill4agent add bmthd/dotfiles dotfiles

SKILL.md Content

View Translation Comparison →

Dotfiles

Two directions of work against

bmthd/dotfiles

. They are opposites and must not be confused:

pr

changes the repository for every machine,

apply

changes this one machine to match the repository.

Subcommand	Direction	Read
`pr <change>`	repository ← change, opened as a PR	pr.md
`apply`	this machine ← repository	apply.md

Read the subcommand's file before doing anything. The procedures are detailed and neither is safe to improvise.

Routing

```
args
```
starts with
```
pr
```
— the rest is the change to make. If nothing follows, ask what to change.
```
args
```
starts with
```
apply
```
(or is empty and the user is reacting to an update notification) — read apply.md.
Neither, and the intent is unclear: ask which one. Do not guess from the current directory — being inside a dotfiles checkout does not mean the user wants
```
pr
```
.

Repository facts

Both subcommands rely on these.

Setup logic lives in
.mise.toml
, not
```
install.sh
```
.
```
install.sh
```
is only a bootstrapper (install mise → place the config →
```
mise install
```
→
```
mise run setup
```
). Changes to tools, environment, or setup steps belong in
```
.mise.toml
```
.
.mise.toml
is installed to
~/.config/mise/config.toml
as the global mise config, so its tasks run from any directory.
Most skills are no longer in this repository. The portable ones moved to
```
bmthd/skills
```
. What remains under
```
.agents/skills/
```
is this
```
dotfiles
```
skill, which only makes sense against this repository. Third-party skills are installed from their upstream by the
```
setup:skills
```
task rather than vendored.

CI (
.github/workflows/quality.yml
) runs

mise ls

,

mise tasks ls

, ShellCheck,

bash -n

,

zsh -n

, and the scripts under

tests/

.