tom-doerr/dotfiles

0

/ 100

Documentation55
Engineering29
Health68
Shell2791d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

Contains my configuration files

Documentation

55

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

29

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (tests).

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 19
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 279
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files43 root entries
  • .claude
  • ghostty
  • hypr
  • i3
  • keyboard_config
  • nvim
  • scripts
  • swaync
  • systemd
  • terminalizer
  • tests
    Good: Test files detected (tests).
  • tmux
  • UltiSnips
  • waybar
  • .gitignore
    Good: .gitignore present.
  • .xscreensaver
  • AGENTS.md
  • aider_model_settings.yml
  • aider.conf.yml
  • aider.model.settings.yml
  • alias.sh
  • bashrc_custom.sh
  • claude-settings.json
  • CLAUDE.md
  • display_layout.sh
  • i3blocks.conf
  • inputrc
  • instruction.md
  • ipython_config.py
  • kitty_desktop.conf.old
  • kitty_thinkpad_x1.conf
  • kitty.conf
  • nvidia-driver-check.sh
  • picom.conf
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • setup.sh
  • shell_functions.sh
  • shell_settings.sh
  • timewarrior.cfg
  • vimium-options.json
  • vimrc.archive
  • zathurarc
  • zshrc_custom.sh