# Code Quality Tools

Here's some commands to help with code quality. You can use them as a one-time clean up and then use them as part of your regular build to maintain your coding rules.

## Normalize Indents (Tabs vs Spaces)

Ahh, the age-old debate of tabs vs spaces. Make sure you have a solid discussion with your team and decide which one is correct (tabs, obviously!) and then use this command to implement it across your entire code base.

### From the CLI

```
utils normalize-indents **.cf?
```

### From CFML

```
command( 'indents' )
    .params( '**.cf*' )
    .run();
```

## Remove Trailing Spaces

Removes trailing whitespace from the ends of your lines.

### From the CLI

```
utils remove-trailing-spaces **.cf*
```

### From CFML

```javascript
command( 'rts' )
    .params( '**.cf*' )
    .run();
```

## Add final EOL character

Makes sure the last line of every source file has an EOL character.

### From the CLI

```
utils add-eol-at-eof **.cf*
```

### From CFML

```javascript
command( 'eol' )
    .params( '**.cf*' )
    .run();
```


---

# 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://commandbox.ortusbooks.com/5.3.0/helpful-commands/code-quality-tools.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.