Who it is forA developer contributing to or modifying Aurelio who needs to confirm changes before committing.
The problemChanges to the backend or frontend can break behavior that is not obvious until tests are run.
The outcomePassing backend and frontend test results, plus a running development server with hot reload.
What you need first
- Git installed
- Node.js 22 or later
- uv installed (https://docs.astral.sh/uv/getting-started/installation/)
- macOS, Linux, or Windows with PowerShell
- For the AI advisor only: an OpenRouter account with credit and an API key
Steps
- Install Git, Node.js 22 or later, and uv, then clone the repository and
cd aurelio-finance. - Run
uv run pytestinside thebackend/folder. - Run
npm testinside thefrontend/folder. - For hot reload, run
uv run uvicorn app.main:app --port 8000inbackend/. - In a second terminal, run
npm run devinfrontend/.
Prompt for your agent
In the aurelio-finance repository, run `uv run pytest` in backend/ and `npm test` in frontend/ on <target branch> and report the pass and fail counts for each. Verify that both commands exit with success before reporting the branch as ready.
Caveat. The README names Node.js 22 or later and uv as prerequisites, so older Node versions may fail before the tests run.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page