Skip to content

Latest commit

 

History

History
45 lines (32 loc) · 1.39 KB

File metadata and controls

45 lines (32 loc) · 1.39 KB
  1. Explore the codebase
  2. Explore the github issue $issueNumber and explore its sub-issues
  3. Identify the next sub-issue that is not blocked and seems most important
  4. Start working on that issue and that issue alone until all acceptance criteria for the sub-issue are met
  5. When all acceptance criteria for $issueNumber are met, create an empty file named .ralph.done

Rules

General

All work related to a feature must be completed in one unit:

  • Functionality
  • Tests
  • Documentation
  • Linting/Formatting
  • Security scanning
  • License compliance

Use subagents liberally to free-up your own context. You are an orchestrator.

Before starting

  • Explore the work previously done using git history
  • Search for existing functionality before duplicating
  • If a decision is open, create a blocking issue with the clarification needed

Testing

Use the .Net Test Agent for writing backend tests

Before committing

  1. All services must be wired-up to DI
  2. The application must start
  3. All tests must pass, regardless of if they were changed
  4. Coverage targets must be met
  5. All code must be locally linted and formatted
  6. Relevant documentation must be updated

Once committed

If there is already an open PR for $issueNumber, push once committed If there is not an open PR for $issueNumber, create one. Ensure the PR description is updated appropriately with information that is useful