> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/demisto-sdk-development-guide/demisto-sdk-guide/install-demisto-sdk/create-a-preset-custom-command-configuration.md).

# Create a preset custom command configuration

Create a custom configuration for demisto-sdk commands.

You can create your own configuration for the demisto-sdk commands by creating a file named **`.demisto-sdk-conf`** within the directory from which you run the commands. This file enables you to set a default value to the existing command flags that take effect whenever the command is run. Use the following structure in the file:

```programlisting
[command_name]
flag_name=flag_default_value
```

{% hint style="info" %}

### Note

Use the flag's full name. If there is a dash - in the flag name, change that to an underscore \_. For example, instead of no-docker-checks use no\_docker\_checks.
{% endhint %}

The following are examples of preset custom command configurations in the **`.demisto-sdk-conf`** file.

* If you prefer to run the pre-commit command only on committed files:

  ```programlisting
  [pre-commit]
  committed_only=true
  ```
* If you want to include untracked Git files in your validation when running the validate command:

  ```programlisting
  [validate]
  include_untracked=true
  ```
* If you want to automatically use minor version changes when running the **`update-release-notes`** command:

  ```programlisting
  [update-release-notes]
  update_type=minor
  ```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/demisto-sdk-development-guide/demisto-sdk-guide/install-demisto-sdk/create-a-preset-custom-command-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.