> For the complete documentation index, see [llms.txt](https://kb.packfiles.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.packfiles.io/using-warp/migration-hq/github-copilot-agent/validate-configuration.md).

# Validate Configuration

**The&#x20;*****Validate Configuration*****&#x20;skill reads your `config/warp.yml`, validates it against Warp's configuration schema, and posts a structured findings report so you can merge configuration changes with confidence.**

Warp's configuration file supports a range of settings: repository visibility, Azure Pipelines rewiring, access policies, custom task checklists, and scripts. As configurations grow more complex, it becomes easy to introduce errors that only surface at runtime. The agent catches those issues before they do.

## How to Use It

1. Open a pull request that modifies `config/warp.yml`.
2. Post a comment on the pull request mentioning the **Packfiles Warp** agent and ask it to *"validate the configuration."*

#### Example:

> *"@packfiles-warp Can you validate the config changes in this PR?"*

The agent reads the current contents of `config/warp.yml` from the pull request's branch, validates it, and posts a review comment on the pull request with its findings.

## Finding Severity Levels

Each finding in the report is assigned one of three severity levels:

* **✅ Valid** — the configuration is correct and there are no concerns
* **⚠️ Warning** — the configuration is syntactically valid, but has implications worth reviewing before merging
* **❌ Error** — the configuration is incorrect or will prevent Warp from working as intended; must be fixed before merging

## Security Checks

Beyond schema validation, the agent flags configuration changes that could have security implications.

These are surfaced as warnings rather than errors, since they may be intentional. The report explains the implication so you can make an informed decision before merging.

## Further Reading

* [Warp.yml](/using-warp/migration-hq/warp.yml.md) — Full configuration reference
* [Access Policies](/using-warp/migration-hq/access-policies.md) — How to configure slash command and issue policies
* [Custom Tasks](/using-warp/migration-hq/custom-tasks.md) — How to define label-triggered checklists
* [Custom Scripts](/using-warp/migration-hq/custom-scripts.md) — How to register and run automation scripts


---

# 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://kb.packfiles.io/using-warp/migration-hq/github-copilot-agent/validate-configuration.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.
