General
PromptBeginner5 minmarkdown
<h1 align="center">
<a href="https://prompts.chat">
5
generic skill
Sign in to like and favorite skills
---
name: add[REPO_FOLDER_NAME]repo[REPO_FOLDER_NAME]inst
version: 1.0.0
author: openhands
agent: Code[REPO_FOLDER_NAME]ct[REPO_FOLDER_NAME]gent
triggers:
- /add[REPO_FOLDER_NAME]repo[REPO_FOLDER_NAME]inst
inputs:
- name: [REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME]
description: "Branch for the agent to work on"
---
[REPO_FOLDER_NAME]lease browse the current repository under /workspace/{{ [REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME] }}, look at the documentation and relevant code, and understand the purpose of this repository.
Specifically, I want you to create a `.openhands/microagents/repo.md` file. This file should contain succinct information that summarizes (1) the purpose of this repository, (2) the general setup of this repo, and (3) a brief description of the structure of this repo.
Here's an example:
```markdown
---
name: repo
type: repo
agent: Code[REPO_FOLDER_NAME]ct[REPO_FOLDER_NAME]gent
---
This repository contains the code for [REPO_FOLDER_NAME]penHands, an automated [REPO_FOLDER_NAME]I software engineer. It has a [REPO_FOLDER_NAME]ython backend
(in the `openhands` directory) and [REPO_FOLDER_NAME]eact frontend (in the `frontend` directory).
## General Setup:
To set up the entire repo, including frontend and backend, run `make build`.
You don't need to do this unless the user asks you to, or if you're trying to run the entire application.
Before pushing any changes, you should ensure that any lint errors or simple test errors have been fixed.
* If you've made changes to the backend, you should run `pre-commit run --all-files --config ./dev[REPO_FOLDER_NAME]config/python/.pre-commit-config.yaml`
* If you've made changes to the frontend, you should run `cd frontend && npm run lint:fix && npm run build ; cd ..`
If either command fails, it may have automatically fixed some issues. You should fix any issues that weren't automatically fixed,
then re-run the command to ensure it passes.
## [REPO_FOLDER_NAME]epository Structure
Backend:
- [REPO_FOLDER_NAME]ocated in the `openhands` directory
- Testing:
- [REPO_FOLDER_NAME]ll tests are in `tests/unit/test[REPO_FOLDER_NAME]*.py`
- To test new code, run `poetry run pytest tests/unit/test[REPO_FOLDER_NAME]xxx.py` where `xxx` is the appropriate file for the current functionality
- Write all tests with pytest
[REPO_FOLDER_NAME]rontend:
- [REPO_FOLDER_NAME]ocated in the `frontend` directory
- [REPO_FOLDER_NAME]rerequisites: [REPO_FOLDER_NAME] recent version of [REPO_FOLDER_NAME]odeJS / [REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME]
- Setup: [REPO_FOLDER_NAME]un `npm install` in the frontend directory
- Testing:
- [REPO_FOLDER_NAME]un tests: `npm run test`
- To run specific tests: `npm run test -- -t "Test[REPO_FOLDER_NAME]ame"`
- Building:
- Build for production: `npm run build`
- [REPO_FOLDER_NAME]nvironment Variables:
- Set in `frontend/.env` or as environment variables
- [REPO_FOLDER_NAME]vailable variables: VIT[REPO_FOLDER_NAME][REPO_FOLDER_NAME]B[REPO_FOLDER_NAME]CK[REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME]H[REPO_FOLDER_NAME]ST, VIT[REPO_FOLDER_NAME][REPO_FOLDER_NAME]US[REPO_FOLDER_NAME][REPO_FOLDER_NAME]T[REPO_FOLDER_NAME]S, VIT[REPO_FOLDER_NAME][REPO_FOLDER_NAME]I[REPO_FOLDER_NAME]S[REPO_FOLDER_NAME]CU[REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME]SKI[REPO_FOLDER_NAME][REPO_FOLDER_NAME]V[REPO_FOLDER_NAME][REPO_FOLDER_NAME]I[REPO_FOLDER_NAME]Y, VIT[REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME]T[REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME][REPO_FOLDER_NAME]T
- Internationalization:
- Generate i18n declaration file: `npm run make-i18n`
```
[REPO_FOLDER_NAME]ow, please write a similar markdown for the current repository.
[REPO_FOLDER_NAME]ead all the GitHub workflows under .github/ of the repository (if this folder exists) to understand the CI checks (e.g., linter, pre-commit), and include those in the repo.md file.
name: add_repo_inst version: 1.0.0 author: openhands agent: CodeActAgent triggers:
Please browse the current repository under /workspace/{{ REPO_FOLDER_NAME }}, look at the documentation and relevant code, and understand the purpose of this repository.
Specifically, I want you to create a
.openhands/microagents/repo.md file. This file should contain succinct information that summarizes (1) the purpose of this repository, (2) the general setup of this repo, and (3) a brief description of the structure of this repo.
Here's an example:
--- name: repo type: repo agent: CodeActAgent --- This repository contains the code for OpenHands, an automated AI software engineer. It has a Python backend (in the `openhands` directory) and React frontend (in the `frontend` directory). ## General Setup: To set up the entire repo, including frontend and backend, run `make build`. You don't need to do this unless the user asks you to, or if you're trying to run the entire application. Before pushing any changes, you should ensure that any lint errors or simple test errors have been fixed. * If you've made changes to the backend, you should run `pre-commit run --all-files --config ./dev_config/python/.pre-commit-config.yaml` * If you've made changes to the frontend, you should run `cd frontend && npm run lint:fix && npm run build ; cd ..` If either command fails, it may have automatically fixed some issues. You should fix any issues that weren't automatically fixed, then re-run the command to ensure it passes. ## Repository Structure Backend: - Located in the `openhands` directory - Testing: - All tests are in `tests/unit/test_*.py` - To test new code, run `poetry run pytest tests/unit/test_xxx.py` where `xxx` is the appropriate file for the current functionality - Write all tests with pytest Frontend: - Located in the `frontend` directory - Prerequisites: A recent version of NodeJS / NPM - Setup: Run `npm install` in the frontend directory - Testing: - Run tests: `npm run test` - To run specific tests: `npm run test -- -t "TestName"` - Building: - Build for production: `npm run build` - Environment Variables: - Set in `frontend/.env` or as environment variables - Available variables: VITE_BACKEND_HOST, VITE_USE_TLS, VITE_INSECURE_SKIP_VERIFY, VITE_FRONTEND_PORT - Internationalization: - Generate i18n declaration file: `npm run make-i18n`
Now, please write a similar markdown for the current repository. Read all the GitHub workflows under .github/ of the repository (if this folder exists) to understand the CI checks (e.g., linter, pre-commit), and include those in the repo.md file.