You're given a task to write a collection of rules, context and guidelines on the repository you're provided. Please gather context on the following categories, then write an AGENTS.md file in the root of the repository.
- General Rules: These are general rules any developer/agent should follow when writing code. It should contain rules such as "When creating new XYZ functions, always first search in the XYZ/ directory to see if one exists, and if not, create it and place it in an existing or new file". Additionally, here is where you'd include context about scripts which are commonly executed, such as linter and formatter scripts.
- Repository Structure: This section is where you'll include high level context about how the repository is laid out, any highly useful and not overly obvious information about how the directories/files are structured, different apps/packages/services inside the repository, etc. Do not include every last detail about the repository contents, only a high level technical overview on the repository structure.
- Dependencies and Installation: This section should include high level context about how to install dependencies, where to install them, package managers, etc. Do not include overly verbose context in this section as most repositories typically have straightforward dependency management.
- Testing Instructions: A general guide on testing in this repository. It should include context such as testing frameworks, roughly what types of modules should be tested, how to run tests, and any other context a developer wouldn't be able to infer by looking at test files on how to write & run tests. Do not include every last detail about testing in this section, only the most used/important context necessary to run tests.
Ensure each category is properly wrapped in opening and closing XML tags. The tags to use are as follows:
<general_rules>
</general_rules>
<repository_structure>
</repository_structure>
<dependencies_and_installation>
</dependencies_and_installation>
<testing_instructions>
</testing_instructions>
It is incredibly important that you ALWAYS wrap your sections in the opening and closing XML tags. Failure to do so will result in an invalid file and will not be accepted.
The file should not contain any other content besides those tags, and the rules/context/instructions they contain. Ensure your rules are thoughtful, concise and actually useful to a developer who's never contributed to the repository before. You can think of it as a more structured and directed CONTRIBUTING.md file.
With all of this in mind, please explore the repository and write this single AGENTS.md file with the rules/context/instructions gathered!
Agent Context
{
"tasks": [
{
"id": "be4968e0-ea74-4a10-aa03-7a181134350a",
"taskIndex": 0,
"request": "[original issue]\n**New Open SWE Request**\nYou're given a task to write a collection of rules, context and guidelines on the repository you're provided. Please gather context on the following categories, then write an `AGENTS.md` file in the root of the repository.\n\n- **General Rules**: These are general rules any developer/agent should follow when writing code. It should contain rules such as \"When creating new XYZ functions, always first search in the XYZ/ directory to see if one exists, and if not, create it and place it in an existing or new file\". Additionally, here is where you'd include context about scripts which are commonly executed, such as linter and formatter scripts.\n- **Repository Structure**: This section is where you'll include high level context about how the repository is laid out, any highly useful and not overly obvious information about how the directories/files are structured, different apps/packages/services inside the repository, etc. Do not include every last detail about the repository contents, only a high level technical overview on the repository structure.\n- **Dependencies and Installation**: This section should include high level context about how to install dependencies, where to install them, package managers, etc. Do not include overly verbose context in this section as most repositories typically have straightforward dependency management. \n- **Testing Instructions**: A general guide on testing in this repository. It should include context such as testing frameworks, roughly what types of modules should be tested, how to run tests, and any other context a developer wouldn't be able to infer by looking at test files on how to write & run tests. Do not include every last detail about testing in this section, only the most used/important context necessary to run tests.\n\nEnsure each category is properly wrapped in opening and closing XML tags. The tags to use are as follows:\n\n\n\n\n\n\n\n\n\nIt is incredibly important that you ALWAYS wrap your sections in the opening and closing XML tags. Failure to do so will result in an invalid file and will not be accepted.\n\nThe file should not contain any other content besides those tags, and the rules/context/instructions they contain. Ensure your rules are thoughtful, concise and actually useful to a developer who's never contributed to the repository before. You can think of it as a more structured and directed `CONTRIBUTING.md` file.\n\nWith all of this in mind, please explore the repository and write this single `AGENTS.md` file with the rules/context/instructions gathered!",
"title": "Create AGENTS.md with Repository Guidelines",
"createdAt": 1752021271547,
"completed": false,
"planRevisions": [
{
"revisionIndex": 0,
"plans": [
{
"index": 0,
"plan": "Create a new file named AGENTS.md in the root of the repository.",
"completed": true,
"summary": "- Created a new file named `AGENTS.md` in the root of the repository to serve as a foundation for adding guidelines and context about the repository in subsequent tasks."
},
{
"index": 1,
"plan": "In AGENTS.md, add a section with the following guidelines: - Always check the existing functions in the root directory before creating new ones. - Use the build script 'npm run build' to compile the project. - Follow the commit and push process outlined in .github/build-and-push.sh for updates.",
"completed": false
},
{
"index": 2,
"plan": "Add a section in AGENTS.md describing: - The main entry point is index.js, which sets up a k3s cluster. - The wait.js file provides a delay function. - The dist directory contains the compiled output. - The .github directory contains workflow and build scripts.",
"completed": false
},
{
"index": 3,
"plan": "Include a section in AGENTS.md: - Use Node.js and npm for managing dependencies. - Install dependencies using 'npm install'. - Key dependencies include node-fetch, @actions/core, @actions/exec, @actions/github, and execa.",
"completed": false
},
{
"index": 4,
"plan": "Add a section in AGENTS.md: - Note that the current test script in package.json is a placeholder and exits with an error. - Testing is set up in .github/workflows/test.yml, which runs on specific branch pushes. - Tests involve setting up a k3s cluster and verifying node readiness.",
"completed": false
}
],
"createdAt": 1752021271547,
"createdBy": "agent"
}
],
"activeRevisionIndex": 0
}
],
"activeTaskIndex": 0
}
You're given a task to write a collection of rules, context and guidelines on the repository you're provided. Please gather context on the following categories, then write an
AGENTS.mdfile in the root of the repository.Ensure each category is properly wrapped in opening and closing XML tags. The tags to use are as follows:
<general_rules>
</general_rules>
<repository_structure>
</repository_structure>
<dependencies_and_installation>
</dependencies_and_installation>
<testing_instructions>
</testing_instructions>
It is incredibly important that you ALWAYS wrap your sections in the opening and closing XML tags. Failure to do so will result in an invalid file and will not be accepted.
The file should not contain any other content besides those tags, and the rules/context/instructions they contain. Ensure your rules are thoughtful, concise and actually useful to a developer who's never contributed to the repository before. You can think of it as a more structured and directed
CONTRIBUTING.mdfile.With all of this in mind, please explore the repository and write this single
AGENTS.mdfile with the rules/context/instructions gathered!Agent Context
{ "tasks": [ { "id": "be4968e0-ea74-4a10-aa03-7a181134350a", "taskIndex": 0, "request": "[original issue]\n**New Open SWE Request**\nYou're given a task to write a collection of rules, context and guidelines on the repository you're provided. Please gather context on the following categories, then write an `AGENTS.md` file in the root of the repository.\n\n- **General Rules**: These are general rules any developer/agent should follow when writing code. It should contain rules such as \"When creating new XYZ functions, always first search in the XYZ/ directory to see if one exists, and if not, create it and place it in an existing or new file\". Additionally, here is where you'd include context about scripts which are commonly executed, such as linter and formatter scripts.\n- **Repository Structure**: This section is where you'll include high level context about how the repository is laid out, any highly useful and not overly obvious information about how the directories/files are structured, different apps/packages/services inside the repository, etc. Do not include every last detail about the repository contents, only a high level technical overview on the repository structure.\n- **Dependencies and Installation**: This section should include high level context about how to install dependencies, where to install them, package managers, etc. Do not include overly verbose context in this section as most repositories typically have straightforward dependency management. \n- **Testing Instructions**: A general guide on testing in this repository. It should include context such as testing frameworks, roughly what types of modules should be tested, how to run tests, and any other context a developer wouldn't be able to infer by looking at test files on how to write & run tests. Do not include every last detail about testing in this section, only the most used/important context necessary to run tests.\n\nEnsure each category is properly wrapped in opening and closing XML tags. The tags to use are as follows:\n\n\n\n\n\n\n\n\n\nIt is incredibly important that you ALWAYS wrap your sections in the opening and closing XML tags. Failure to do so will result in an invalid file and will not be accepted.\n\nThe file should not contain any other content besides those tags, and the rules/context/instructions they contain. Ensure your rules are thoughtful, concise and actually useful to a developer who's never contributed to the repository before. You can think of it as a more structured and directed `CONTRIBUTING.md` file.\n\nWith all of this in mind, please explore the repository and write this single `AGENTS.md` file with the rules/context/instructions gathered!", "title": "Create AGENTS.md with Repository Guidelines", "createdAt": 1752021271547, "completed": false, "planRevisions": [ { "revisionIndex": 0, "plans": [ { "index": 0, "plan": "Create a new file named AGENTS.md in the root of the repository.", "completed": true, "summary": "- Created a new file named `AGENTS.md` in the root of the repository to serve as a foundation for adding guidelines and context about the repository in subsequent tasks." }, { "index": 1, "plan": "In AGENTS.md, add a section with the following guidelines: - Always check the existing functions in the root directory before creating new ones. - Use the build script 'npm run build' to compile the project. - Follow the commit and push process outlined in .github/build-and-push.sh for updates.", "completed": false }, { "index": 2, "plan": "Add a section in AGENTS.md describing: - The main entry point is index.js, which sets up a k3s cluster. - The wait.js file provides a delay function. - The dist directory contains the compiled output. - The .github directory contains workflow and build scripts.", "completed": false }, { "index": 3, "plan": "Include a section in AGENTS.md: - Use Node.js and npm for managing dependencies. - Install dependencies using 'npm install'. - Key dependencies include node-fetch, @actions/core, @actions/exec, @actions/github, and execa.", "completed": false }, { "index": 4, "plan": "Add a section in AGENTS.md: - Note that the current test script in package.json is a placeholder and exits with an error. - Testing is set up in .github/workflows/test.yml, which runs on specific branch pushes. - Tests involve setting up a k3s cluster and verifying node readiness.", "completed": false } ], "createdAt": 1752021271547, "createdBy": "agent" } ], "activeRevisionIndex": 0 } ], "activeTaskIndex": 0 }