# Release Engineering

- [Introduction](https://engineering.obvious.in/release-engineering/introduction.md): RE (Release Engineering) is the difference between building software in small teams/startups and manufacturing software in an industrial way that is repeatable, gives predictable results, and scales w
- [Git commit messages](https://engineering.obvious.in/release-engineering/git-commit-messages.md): Writing clear and concise git commit messages is important to the overall health of a project and the team that is working on the project.
- [Code reviews & pull requests](https://engineering.obvious.in/release-engineering/code-reviews-and-pull-requests.md): Regular, team-wide code reviews are important for the health of the software being built.
- [Trunk-based development](https://engineering.obvious.in/release-engineering/trunk-based-development.md): From Feature-based Delivery to Timeline-based Delivery. See trunkbaseddevelopment.com for the official documentation.
- [Our methodology](https://engineering.obvious.in/release-engineering/trunk-based-development/our-methodology.md): Following "pure" TBD is difficult without a lot of tooling, so here's the lightweight approach that we follow that relies on team discipline.
- [Service Dependencies](https://engineering.obvious.in/release-engineering/service-dependencies.md): List of services Obvious has used in past projects
- [Tooling & infrastructure](https://engineering.obvious.in/release-engineering/tooling-infrastructure.md)
- [Git commands & workflows](https://engineering.obvious.in/release-engineering/git-commands-workflows.md): List of Git commands and workflows we generally use


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://engineering.obvious.in/release-engineering.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
