# Contribution Guidelines

- [Overview](https://docs.kleros.io/contribution-guidelines/overview.md): Welcome to the contribution guide for all software pertaining to Kleros.
- [General Dev. Workflow](https://docs.kleros.io/contribution-guidelines/general-dev.-workflow.md): How we keep track of new development work and push new code.
- [Task Tracking & Lifecycle](https://docs.kleros.io/contribution-guidelines/general-dev.-workflow/task-tracking-and-lifecycle.md): Our methodology for keeping track of development work.
- [Releases](https://docs.kleros.io/contribution-guidelines/general-dev.-workflow/releases.md): How we push new code to staging, production, and beyond.
- [Smart Contract Workflow](https://docs.kleros.io/contribution-guidelines/smart-contract-workflow.md): The specificities of Smart Contract development for Kleros.
- [Task Tracking & Lifecycle](https://docs.kleros.io/contribution-guidelines/smart-contract-workflow/task-tracking-and-lifecycle.md): Smart contract development poses unique challenges and experience has taught us that not all the rules of traditional software apply.
- [RAB - Review, Audit, Bounty](https://docs.kleros.io/contribution-guidelines/smart-contract-workflow/rab.md): The margin of error in smart contract development is almost non-existent, due to the value of their transactions. This is how we make sure our contracts are airtight, to the best of our abilities.
- [RABd (+ Deploy)](https://docs.kleros.io/contribution-guidelines/smart-contract-workflow/rabd.md): Read this before hitting the big red button.
- [Reporting Vulnerabilities](https://docs.kleros.io/contribution-guidelines/smart-contract-workflow/reporting-vulnerabilities.md): When you find something wrong with a contract.
- [Code Style and Guidelines](https://docs.kleros.io/contribution-guidelines/code-style-and-guidelines.md): Keep your code compliant to Kleros' standards.
- [Git](https://docs.kleros.io/contribution-guidelines/code-style-and-guidelines/git.md): Controlling version control.
- [Solidity](https://docs.kleros.io/contribution-guidelines/code-style-and-guidelines/solidity.md): Our standards for smart contract code.
- [Web Languages](https://docs.kleros.io/contribution-guidelines/code-style-and-guidelines/web-languages.md): How we handle the ever changing suite of tools and frameworks.
- [License & Code of Conduct](https://docs.kleros.io/contribution-guidelines/license-and-code-of-conduct.md): Kleros is open-sourced, MIT licensed and a civilized collaboration space.
- [License](https://docs.kleros.io/contribution-guidelines/license-and-code-of-conduct/license.md): MIT, period.
- [Code of Conduct](https://docs.kleros.io/contribution-guidelines/license-and-code-of-conduct/code-of-conduct.md): We foster an open and welcoming environment.


---

# 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://docs.kleros.io/contribution-guidelines.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.