From 7cb869175e3d3fb600b14288b2840340dca2aa22 Mon Sep 17 00:00:00 2001 From: Kim T Date: Fri, 23 Jan 2026 21:32:28 -0800 Subject: [PATCH 1/3] Add AGENTS.md --- AGENTS.md | 91 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000..e560265 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,91 @@ +# Instructions for Agents: Contributing to Open Audio Stack Registry via Command Line + +## Fork the Repository + +Use GitHub CLI to fork the repository: + +```bash +gh repo fork open-audio-stack/open-audio-stack-core --clone +cd open-audio-stack-core +``` + +## Setup + +Install dependencies: + +```bash +npm install +``` + +## Create a Branch + +Create and switch to a new branch for your contribution. Use descriptive branch names following these conventions: + +- `feature/feature-name` for new features +- `fix/fix-name` for bug fixes + +Example: + +```bash +git checkout -b feature/feature-name +``` + +## Contributing functional changes + +Edit TypeScript/JavaScript files in the codebase using your tools. Ensure changes follow the project's coding standards, enforced by Prettier (.prettierrc.json) for code formatting, ESLint (eslint.config.js) for linting, and Vitest (vitest.config.ts) for the test suite. + +Then proceed to the Validate Changes, Commit Changes, Push Changes, and Submit Pull Request sections below. + +## Validate Changes + +Run formatting, linting, tests and build commands to validate your changes: + +```bash +npm run format +npm run lint +npm test +npm run build +``` + +Verify that all tests pass and there are no linting errors. + +Return a summary of the changes to the user for them to read/review. + +Ask user for [Y/N] approval to proceed to Commit Changes, Push Changes and Submit Pull Request. + +- If the user answers Yes or Y, continue to Commit Changes, Push Changes and Submit Pull Request steps below. +- If the user answers No or N, ask them what changes they would like to make, and iterate until they are happy with the result, each time asking for approval to continue to next steps. + +## Commit Changes + +Stage and commit your changes. Use descriptive commit messages with prefixes following these conventions: + +- `[feature]` for new features +- `[fix]` for bug fixes + +Example: + +```bash +git add . +git commit -m "[feature] Feature name. Add descriptive commit message for your changes" +``` + +## Push Changes + +Push the branch to your forked repository: + +```bash +git push origin feature/feature-name +``` + +## Submit Pull Request + +Create a pull request using GitHub CLI: + +```bash +gh pr create --title "Your PR Title" --body "Description of your changes" +``` + +## Conclusion + +Respond to the user that the contribution has been submitted for review, with the url to the PR for them to monitor updates. From 4dd9bc0b7c01ad26b9f7f6eb414183c3ecf8229b Mon Sep 17 00:00:00 2001 From: Kim T Date: Fri, 23 Jan 2026 21:34:06 -0800 Subject: [PATCH 2/3] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 82f3f8b..adb3fe4 100644 --- a/README.md +++ b/README.md @@ -80,6 +80,8 @@ Open Audio Stack Core was built using: - prettier 3.x - vitest 1.x +If using a coding agent point it at `AGENTS.md` to automate the process of making changes. + ## Developer installation To install, build and run code locally, first install dependencies: From c6d133d0f91592754625d231aaef8bc47cfdab67 Mon Sep 17 00:00:00 2001 From: Kim T Date: Fri, 23 Jan 2026 21:35:05 -0800 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index adb3fe4..aaf4d09 100644 --- a/README.md +++ b/README.md @@ -78,7 +78,7 @@ Open Audio Stack Core was built using: - TypeScript 5.x - eslint 9.x - prettier 3.x -- vitest 1.x +- vitest 3.x If using a coding agent point it at `AGENTS.md` to automate the process of making changes.