# Related topics

Once you're familiar with the topics covered under [Cover Pipeline for GitHub](/features/cover-pipeline/cover-pipeline-for-github.md), check out the following to help extend your unit test capabilities even further:

* **Specs & Reqs**\
  Specifications, prerequisites, and general project requirements are all covered in [Specs & Reqs](/get-started/specs-and-reqs.md).
* **Cover Reports Integration**\
  Additional `coverage-reports` and `upload` commands can be added to your workflow in order to integrate **Diffblue Cover: Baseline** labelled CI runs into [Cover Reports](/features/cover-reports.md)- see [Generate and upload reports bundles](/features/cover-reports/cover-reports-contributor/reports-bundles.md)for details.
* **`dcover` Commands in a pipeline**\
  Additional optional arguments can be used with the `validate` and `create` commands listed in the workflow YAML file for your project - see [Commands & Arguments](/features/cover-cli/commands-and-arguments.md) for details.
* **Output Codes**\
  Diffblue Cover performs a number of checks before, during, and after creating unit tests. Cover can generate a range of output codes during these checks to provide general information and highlight any issues. These codes and associated messages are output during the run, visible in the job output, and saved to the log files. See [Output Codes](/features/output-codes.md) for details.
* **Test Coverage**\
  See the [How to Increase Code Coverage with Diffblue Cover (Step-by-Step)](/features/tutorials/increase-code-coverage.md) topic for general information on ways to improve your overall coverage across your Java projects.
* **Developer Tools**\
  Diffblue Cover is also available as two developer tools - Cover Plugin for IntelliJ (write tests directly within the IntelliJ IDE) and Cover CLI (full command line tool) - both of which are bundled with Cover Pipeline for GitHub. These tools can be used by your development staff to automatically write tests during the development stages of a project, thereby allowing them to check for regressions and unplanned code behavior changes even before the code is committed back to GitHub. See the [Free trial](/get-started/get-started/free-trial.md) or [Get started](/get-started/get-started.md) topics to check out the tools for yourself.


---

# 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://cover-docs-preview.diffblue.com/features/cover-pipeline/cover-pipeline-for-github/related-topics.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.