Skip to content
Back to search

dotfiles

paul's fish, bash, git, etc config files. good stuff.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/paulirish/dotfiles with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/paulirish/dotfiles'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/paulirish--dotfiles/badge.svg)](/listings/paulirish--dotfiles)

HTML

<a href="/listings/paulirish--dotfiles"><img src="/api/listings/paulirish--dotfiles/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

I would not suggest you just wholesale use my dotfiles. But there's a few files where there's great goodies you can steal.

shell

This repo contains config for fish and bash. As of 2016, I primarily use `fish` shell, but fall back to `bash` once in a while. The bash and fish stuff are both well maintained. If you're using fish you'll want to do a `git submodule update --init`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 108 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Paul's dotfiles
  2. * I maintain this repo as *my* dotfiles, but I'm keenly aware people are using it for theirs.
  3. * You're quite welcome to make suggestions, however I may decline if it's not of personal value to me.
  4. * If you're starting off anew, consider forking [mathias](https://github.com/mathiasbynens/dotfiles/) or [alrra](https://github.com/alrra/dotfiles/). [paulmillr](https://github.com/paulmillr/dotfiles) and [gf3](https://github.com/gf3/dotfiles) also have great setups
  5. ## Setup
  6. I would not suggest you just wholesale use my dotfiles. But there's a few files where there's great goodies you can steal.
  7. #### shell
  8. This repo contains config for fish and bash. As of 2016, I primarily use `fish` shell, but fall back to `bash` once in a while. The bash and fish stuff are both well maintained. If you're using fish you'll want to do a `git submodule update --init`.
  9. ## my favorite parts.
  10. ### aliases and functions
  11. * [`aliases.fish`](./fish/aliases.fish) and [`functions.fish`](./fish/functions.fish) and [`fish/functions/*`](./fish/functions/)
  12. * [`.aliases`](./.aliases) and [`.functions`](./.functions)
  13. So many goodies.
  14. ### The "readline config" (`.inputrc`)
  15. Basically it makes typing into the prompt amazing.
  16. * tab like crazy for autocompletion that doesnt suck. tab all the things. srsly.
  17. * no more <tab><tab> that says "Display all 1745 possibilities? (y or n)" YAY
  18. * type `cat <uparrow>` to see your previous `cat`s and use them.
  19. * case insensitivity.
  20. * tab all the livelong day.
  21. ### [.gitconfig](./.gitconfig)
  22. * err'body gotta have their aliases. I'm no different.
  23. ### Moving around in folders (`z`, `...`, `cdf`)
  24. `z` helps you jump around to whatever folder. It uses actual real magic to determine where you should jump to. Seperately there's some `...` aliases to shorten `cd ../..` and `..`, `....` etc. Then, if you have a folder open in Finder, `cdf` will bring you to it.
  25. ```sh
  26. z dotfiles
  27. z blog
  28. .... # drop back equivalent to cd ../../..
  29. z public
  30. cdf # cd to whatever's up in Finder
  31. ```
  32. `z` learns only once its installed so you'll have to cd around for a bit to get it taught.
  33. Lastly, I use `open .` to open Finder from this path. (That's just available normally.)
  34. ## overview of files
  35. #### shell environment
  36. * `.aliases`, `.bash_profile`, `.bash_prompt`, `.bashrc`, `.exports`, `.functions`
  37. #### manual run
  38. * `setup-a-new-machine.sh` - random apps i need installed
  39. * `symlink-setup.sh` - sets up symlinks for all dotfiles and vim config.
  40. * `.macos` - run on a fresh mac os setup
  41. * `brew.sh` & `brew-cask.sh` - homebrew initialization
  42. #### git, brah
  43. * `.gitconfig`
  44. * `.gitignore`
  45. ### Sensible OS X defaults in `.macos`
  46. Mathias's repo is the canonical for this, but you should probably run his or mine after reviewing it.
  47. ### `~/bin`
  48. One-off binaries that aren't via an npm global or homebrew. [git open](https://github.com/paulirish/git-open), `subl` for Sublime Text, and some other git utilities.
  49. ### 2020 update
  50. Rust folks have made a few things that are changing things.
  51. - most folks know `bat` as a `cat` replacement
  52. - https://github.com/dandavison/delta is a bit nicer than the diff-so-fancy project that i started. :/
  53. - https://github.com/eza-community/eza is better `ls` and gets all the trapd00r/LS_COLORS stuff etc.
  54. - https://github.com/bigH/git-fuzzy interactive git thing. deprecates my `git recent` script. and probably some other things.
  55. ### Dotfiles mgmt todo
  56. Also I'd like to migrate to using one of these:
  57. - homesick or
  58. - https://www.atlassian.com/git/tutorials/dotfiles
  59. - https://github.com/nix-community/home-manager
  60. - https://www.chezmoi.io/
  61. also interested in https://github.com/dandavison/open-in-editor
  62. ### SSH authenticate with security key
  63. (presumably you've already upgraded from passwords to using ssh public key authentication.. but this is an alternative if you want the security key challenge)
  64. Been doing this for a while.. forgot how i learned it and nobody has it documented that I can find...
  65. Run on client machine:
  66. ssh-add -L | grep ecdsa-sha2-nistp256@
  67. This outputs a `ecdsa-sha2-nistp256` key for me. I know it's registered for my hardware security key.
  68. Put that in whatever `authorized_keys` of your remote host. That's it.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.