> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/guides.md).

# Guides

- [Identify and improve delivery bottlenecks](https://help.swarmia.com/guides/identify-and-improve-delivery-bottlenecks.md)
- [Understand how engineering time is spent](https://help.swarmia.com/guides/understand-how-engineering-time-is-spent.md)
- [Improve pull request flow](https://help.swarmia.com/guides/improve-pull-request-flow.md): Get visibility into your team’s pull requests and the contributing factors behind cycle time: the number of pull requests in progress, batch size, and review time.
- [Pull request insights](https://help.swarmia.com/guides/improve-pull-request-flow/pull-request-insights.md): Diagnose cycle time issues, decrease review time and improve pull request workflow with Swarmia's pull request insights.
- [Reducing pull request cycle time](https://help.swarmia.com/guides/improve-pull-request-flow/reducing-pull-request-cycle-time.md): Get pull requests through faster with Swarmia's insights and working agreements around cycle time.
- [Review code faster](https://help.swarmia.com/guides/improve-pull-request-flow/review-code-faster.md): Code rarely ages well, and merging doesn’t get any easier over time. Here's how Swarmia helps your team get pull requests through faster.
- [Diagnosing low pull request throughput](https://help.swarmia.com/guides/improve-pull-request-flow/diagnosing-low-pull-request-throughput.md): Throughput is more difficult to improve than for example cycle time, since it reflects the team's overall situation rather than just the process.
- [Analyzing pull request batch size](https://help.swarmia.com/guides/improve-pull-request-flow/analyzing-pull-request-batch-size.md): Batch size measures how much work is bundled up in a change. Swarmia offers tools for evaluating pull request batch size by looking at the total amount of changes.
- [Improve code quality](https://help.swarmia.com/guides/improve-code-quality.md): Build better quality products, reduce technical debt, and implement development practices that scale as your team grows
- [Improve your team's focus](https://help.swarmia.com/guides/improve-your-teams-focus.md)
- [Optimizing issue cycle time](https://help.swarmia.com/guides/improve-your-teams-focus/optimizing-issue-cycle-time.md): Practical tips and best practices for improving your focus and structuring work to reduce issue cycle times.
- [Benchmarks & comparisons](https://help.swarmia.com/guides/benchmarks-and-comparisons.md): Compare your engineering metrics to Swarmia benchmarks, and analyze how different teams compare against your organization's average.
- [Retrospectives with Swarmia](https://help.swarmia.com/guides/retrospective-guide.md): How to run great retrospectives with Swarmia.
- [Improve developer experience](https://help.swarmia.com/guides/improve-developer-experience.md): Spot what's slowing your engineers down — flaky CI, slow feedback loops, unclear priorities, or tooling pain — and fix it.
- [Understand the impact of AI tools](https://help.swarmia.com/guides/understand-the-impact-of-ai-tools.md): Combine developer experience surveys, adoption metrics, and usage patterns to understand how AI coding tools play into your software organization's productivity.
- [Use Swarmia in meetings and team rituals](https://help.swarmia.com/guides/use-swarmia-in-meetings-and-team-rituals.md)
- [Drive continuous improvement](https://help.swarmia.com/guides/drive-continuous-improvement.md): Learn how to use surveys, signals, and working agreements to build a continuous improvement practice your team can own.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.swarmia.com/guides.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.