Ruler Development Process

Apply the Ruler project's development standards: test-driven development, comprehensive testing, code formatting, and branch/PR workflow.

Instructions

1. Testing Requirements

**Test-Driven Development:**

- Unit tests

- Integration tests

- End-to-end tests

**Before implementing features:**

2. Code Formatting

**Prettier:**

**Before committing:**

```bash

npx prettier --write .

```

3. Branch and Pull Request Workflow

**Branching:**

**Pull Requests:**

- Rationale behind the change

- Functional changes made

- Specific files and modules affected

- `npm ci`

- `npm run lint`

- `npm test`

- `npm run build`

**Git Commits:**

```bash

git commit --author="AI <[email protected]>"

```

4. Pre-Commit Checklist

Before every commit, verify:

5. CI Requirements

All pull requests must pass:

1. Dependency installation (`npm ci`)

2. Linting (`npm run lint`)

3. Test suite (`npm test`)

4. Build process (`npm run build`)

Do not mark PR as ready for review until all checks pass.

Example Usage

**Implementing a new feature:**

1. Create feature branch: `git checkout -b feature/new-capability`

2. Write failing tests for the feature

3. Implement minimal code to pass tests

4. Run Prettier: `npx prettier --write .`

5. Verify CI locally: `npm ci && npm run lint && npm test && npm run build`

6. Commit with AI author: `git commit --author="AI <[email protected]>" -m "Add new capability"`

7. Push and create descriptive PR

**Fixing a bug:**

1. Create fix branch: `git checkout -b fix/bug-description`

2. Write test that reproduces the bug (should fail)

3. Fix the bug (test should now pass)

4. Format code with Prettier

5. Commit with AI author attribution

6. Ensure all CI checks pass before PR

Constraints