how to contribute

How to contribute

Contributions to Qredence/fleet-prime-agent land as pull requests on the main branch. The authoritative rules are AGENTS.md at the repository root; read it before starting. This page covers how to find work, the review and merge flow, and the definition of done. See Patterns and conventions for code style, the connection seam, daemon protocol change policy, and changelog format, and Development workflow for the step-by-step cycle.

Finding work

• plans/ holds improve-react audit plans. Each plans/NNN-<slug>.md is a self-contained implementation task with a severity, a status, and any dependencies on other plans; plans/README.md lists the recommended execution order and shared constraints. Pick an unimplemented plan and implement one plan per change.
• GitHub issues carry pkg:* labels to indicate which package is affected. The available labels are pkg:agent, pkg:ai, pkg:coding-agent, and pkg:tui. An issue spanning multiple packages gets all relevant labels.
• UI work under web/ is a standalone Qredence product; do not merge changes there upstream.

Branching

Work happens on feature branches. Create a branch from main, make your changes, and open a pull request. Reviewers and CI analyze the PR without pulling the branch locally first. Do not merge PRs yourself; the requester approves and merges.

Definition of done

A change is done when:

• npm run check passes with no errors, warnings, or infos. Run it after code changes (not documentation-only changes) and read the full output, not the tail. It runs biome check --write --error-on-warnings ., then tsgo --noEmit, then the installer, browser-smoke, rendering, and web checks. It does not run tests.
• Any test files you created or modified pass. If you touch a test file you must run it and iterate until it passes.
• The relevant package CHANGELOG.md has a new flat past-tense bullet under ## [Unreleased], with issue or PR attribution.
• The change complies with AGENTS.md: no inline imports, no any unless necessary, no hardcoded keybinding checks, no edits to packages/ai/src/models.generated.ts, and, for web changes, no @earendil-works/* imports from browser code.
• If the change touches the coding-agent surface the web adapter consumes, web/server is updated in the same change.

Review and merge

• Analyze PRs without pulling locally first.
• If the change is approved, create a feature branch, pull the PR, rebase on main, apply any requested adjustments, commit, merge into main, push, close the PR, and leave a comment in the contributor's tone.
• Work in feature branches until everything is according to the requester's requirements. Never merge PRs by yourself.

Related pages

• Development workflow, branch to merge, git rules, release process
• Testing, frameworks and how to run them
• Debugging, logs, daemon state, common failures
• Tooling, biome, tsgo, husky, and the build scripts
• Patterns and conventions, code style, seam, protocol changes, changelog format
• Getting started, prerequisites and install