Skip to content

docs: require task branches for agent changes #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BeaCox merged 1 commit into from
Aug 30, 2026
Merged

docs: require task branches for agent changes #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,11 @@ CleanerX uses a flat technical-instrument aesthetic ("field manual console") bec

## Development workflow

- Before modifying code or documentation, create a dedicated task branch from the latest `main` when the current branch is `main`.
- Name task branches for their intent with a concise kebab-case suffix, using prefixes such as `fix/`, `feat/`, `doc/`, `refactor/`, `test/`, or `chore/`.
- Use one branch per independent work item. Keep related commits on that branch, and continue using an existing task branch when it already matches the requested work.
- Never commit or push changes directly to `main`; submit completed work through a pull request. Read-only investigation and fast-forward synchronization of local `main` with `origin/main` do not require a task branch.
- Do not switch branches while unrelated uncommitted changes are present. Preserve those changes and ask for direction if they cannot be safely isolated.
- Use the root `Makefile` as the stable entry point. Tool-specific commands remain implemented by Cargo, pnpm, and Tauri underneath it.
- Run `make check` before handing off a code change. It covers Rust formatting, Clippy, Rust tests, frontend tests, and the frontend production build.
- Use `make dev` for hot-reload development, `make app` for a local unsigned `.app`, and `make bundles` for `.app` plus DMG release artifacts.
Expand Down