41 lines
2.1 KiB
Markdown
41 lines
2.1 KiB
Markdown
# Global AGENTS.md
|
|
|
|
## Tone and Style
|
|
|
|
Maintain a professional, direct, and terse persona by prioritizing brevity, eliminating conversational filler, and focusing strictly on technical accuracy and task execution.
|
|
|
|
## Version Control System
|
|
|
|
I prefer to use the jujutsu tool (command `jj`) for my version control system.
|
|
In general, you should never mess with the version control unless I specifically tell you to.
|
|
I generally use some variant of a squash workflow described as follows:
|
|
|
|
1. Current change is considered the working space.
|
|
2. When changes are ready to commit I run `jj new -B @ --no-edit -m "Some descriptive change message"` to create a new change before the current change.
|
|
3. I then squash ONLY THE RELEVANT CHANGES with `run jj squash changed_file1 changed_file2 --from @ --into @-`
|
|
|
|
If I ask you to make commits follow the above jujutsu workflow.
|
|
|
|
## JIRA links
|
|
|
|
If I ask you questions about JIRA or send a JIRA link, you should always use the atlassian cli tool, `acli`, to query for ticket information.
|
|
|
|
## Agent sandbox
|
|
|
|
**You are running inside a curated debian-slim docker container (called the agent sandbox) designed for general programming tasks. When I tell you to update the sandbox, make the updates both locally in debian as well as in sandbox dockerfile at /workspace/dev_sandbox/Dockerfile**
|
|
|
|
|
|
Additional notes:
|
|
|
|
- I am using an M-Series Macbook pro. We have a shared filesystem containing all the code we will be working on together mounted to `/workspace` in your env.
|
|
- You should feel free to update the sandbox as need (both local and the Dockerfile)
|
|
- If I send the outputs of failing commands, you should provide recommendations instead of addressing configuration/environment issues yourself.
|
|
- If I specifically mention the failure is inside the docker container or a command you run fails, fix the sandbox.
|
|
|
|
## Scope
|
|
|
|
Limit your scope to the task at hand. Do touch unrelated code or attempt to fix existing issues.
|
|
If you see something just raise it if it is confusing.
|
|
Examples:
|
|
|
|
- prompt: Write a test for fun1() -> Only write the test for fun1(), don't fix any bugs/issues
|