kaan/dotfiles
1
0
Fork 0
mirror of https://github.com/SeriousBug/dotfiles synced 2026-07-27 12:35:37 -05:00
Code Issues Projects Releases Wiki Activity

Add machine-safety, agents, and commit-often rules to CLAUDE.md; tighten new-work step 2

Browse source 
Claude-Session: https://claude.ai/code/session_01RyUSWPV85RTPNY4H66Jnkw
This commit is contained in:
Kaan Barmore-Genc 2026-06-30 01:52:52 -05:00
parent 57e19ee9cd
commit 9ef9604f61
2 changed files with 16 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
claude/CLAUDE.md
View file

@ -1,5 +1,14 @@
# Personal Claude Code Instructions
## Do not modify my machine without permission
**Never install software, packages, or tools on my machine without explicit permission** — no `brew install`, `npm install -g`, `pip install`, `apt`, downloading binaries, or anything that changes global system state. This is absolutely disallowed. If a task needs a tool I don't have, stop and ask first, or find a way that doesn't touch my machine (e.g. run it in Docker — if Docker is not available then ask me).
## Agents
If work is parallel or cleanly scoped out, consider handing off to subagents to preserve context.
Do **not** use fork subagents. Only separate agents with clear scope or a clear goal.
## Notifying me / sharing images via Discord
The `discord-send` CLI is on my PATH. Use it whenever I ask you to notify me when something is done, or to show me an image or video — send it to my Discord and I'll see it there.
@ -13,6 +22,9 @@ discord-send --attach ./screenshot.png 'Here is the rendered page'
When asked to respond to reviews in a PR, check the PR description and all comments. Check out the PR branch. Decide if any changes are required or not, make changes if needed, commit and push once done. Always push the PR branch if responding to a PR, do not push to a different branch.
## Commits
Commit often. It's better to commit things than to leave changes hanging for a long time. You don't have to commit after every change, but once you're done working just go ahead and commit.
## Writing Style
Following rules are for your writing. Follow these when responding to the user, when writing documentation and code comments, and when writing commit messages or PR descriptions.

7
claude/skills/new-work/SKILL.md
View file

@ -16,9 +16,10 @@ If there are uncommitted changes:
## Step 2: Switch to main and pull latest
- Attempt to check out `main`.
- If that fails because the branch does not exist, check out `master` instead.
- Then pull the latest changes:
- Attempt to check out `main`, or failing that `master`.
- Then pull the latest changes.
You **must** do this. Unless instructed to continue on the same branch, make sure you start from latest main.
## Step 3: Create a new branch