Skip to content
artyomsvPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

dotai

My configuration for AI coding tools: rules, agents, commands, skills and output styles for Claude Code and Codex.

The repository lives anywhere. Install scripts link its content into each tool's home folder, so an edit in either place is an edit to the repository.

Install

# Windows (PowerShell). Folder links need nothing; the one file link (Codex AGENTS.md) needs
# Developer Mode: run `start ms-settings:developers` and turn it on.
git clone https://github.com/artyomsv/dotai.git E:\Projects\dotai
E:\Projects\dotai\scripts\install.ps1 -DryRun
E:\Projects\dotai\scripts\install.ps1
# Linux / macOS
git clone https://github.com/artyomsv/dotai.git ~/Projects/dotai
~/Projects/dotai/scripts/install.sh --dry-run
~/Projects/dotai/scripts/install.sh

The installer never deletes anything: whatever is in the way is moved to ~/.dotai-backup/<timestamp>/, outside every folder a tool loads. Run it again after a pull that adds links. -Uninstall / --uninstall removes only the links that point into this repository and restores the newest backup. Both scripts also turn on the secret-scanning pre-commit hook.

Re-run install.sh after every pull: a pull rewrites changed files and detaches their hard links.

Layout

Path What
claude/ Claude Code: agents/, commands/, rules/, hooks/, output-styles/
codex/ Codex: global AGENTS.md and skills/
shared/ Content every tool reads in the same format, linked into each: skills/pr-review (post inline findings on a GitHub PR, resolve verified fixes, approve or request changes, keep one review: … label per PR)
links/<tool>.links One line per link: <path in repo> <link to create> [files] [scoped] (see Scope)
links/<tool>.project Same, but per personal project, with targets relative to the project root; used only on a machine with ~/.config/dotai/projects
scripts/ install.ps1, install.sh, check-secrets.sh

Adding another AI tool is one new links/<tool>.links file plus a folder for its content. The scripts need no change.

The Codex review-all skill reads its checklists from the Claude agents in ~/.claude/agents/, so install both when you use it.

Scope: personal projects only

On most machines everything links under the tool home (~/.claude, ~/.codex) and applies to every project. A machine that also holds work repositories must not do that: Claude Code reads ~/.claude in every project. On such a machine, list the personal project roots in ~/.config/dotai/projects (one path per line, ~ allowed, never in this repository). When that file exists:

  • Manifest lines tagged scoped are skipped, and a leftover global link from an earlier install is removed. Only hooks/ and output-styles/ stay under ~/.claude: a hook runs only when a settings file names it, and ~/.claude/settings.json runs block-git-identity-override.sh everywhere on purpose.
  • Every listed project that exists on the machine gets the lines of links/claude.project, relative to its root; a listed project that is missing is skipped. The installer adds each link inside a git repository to that repository's .git/info/exclude.

Claude Code reads .claude/ from the working directory up to the repository root and never above it, so a parent folder cannot serve several repositories, and a git worktree is its own root. Tests on 2026-11-02 also showed that .claude/rules ignores symbolic links (a linked folder and linked files alike), that an agents folder behind a symbolic link failed to load once, and that hard-linked files loaded every time, while .claude/commands and .claude/skills follow symbolic links. So rules and agents are hard-linked file by file into a dotai/ subfolder (files in the manifest) and commands and skills are symbolic links. Commands in that subfolder are namespaced: /dotai:review-all, /dotai:blog, and so on. A hard link is the same file as the one in this repository until a pull rewrites it; re-run the installer after every pull. A hard link needs the project on the same disk (volume, drive letter) as this repository.

What stays out

Anything machine-specific or private stays in the tool's home folder and is never linked: settings, credentials, sessions, history, caches, agent memory, and Codex config.toml and rules/. Values a command needs but must not publish (hosts, user names) live in ~/.config/dotai/ — see claude/commands/fix-kubectl.md.

This repository is public. scripts/check-secrets.sh runs as a pre-commit hook and in CI, and blocks private IPs, private hostnames, emails, keys and tokens.

License

MIT

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages