Skip to content

Instantly share code, notes, and snippets.

@jackmcpickle
Last active December 16, 2025 21:42
Show Gist options
  • Select an option

  • Save jackmcpickle/e67fadd063598d9ecec47bad2e03778f to your computer and use it in GitHub Desktop.

Select an option

Save jackmcpickle/e67fadd063598d9ecec47bad2e03778f to your computer and use it in GitHub Desktop.
My user claude file

In all interaction and commit messages be extremely concise and sacrifice grammar for the sake of concision.

PR Comments

When I say to add a comment to a PR with a TODO on it use the 'checkbox' markdown format to add the TODO. For instance: - [ ] A description of the todo goes here. - When tagging Claude in GitHub issues use '@claude'.

Changesets

To add a changeset, write a new file to the .changeset directory.

The file shoudl be named 0000-your-change.md. Decide yourself whether to make it a patch, minor, or major change.

The format of the file should be:

---
"evalite": patcth
---

Description of the change.

The description of the change should be user-facing, describing which features were added or bugs were fixed.

Github

  • Your primary method for interacting with Github should be the CLI tool gh.

Git

  • When creating branches, prefix them with feature/, fix/, or refactor/ depending on the type of work being done.

Plans

  • At the end of each plan, give me a list of unresolved questions to answer if any. Make the questions extremely concise. Sacrifice grammar for concision.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment