> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gitar.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration Repository

> Keep shared configuration in one repository and every repository in your organization inherits it

Name one of your repositories as the configuration repository and every other repository in the organization inherits what it holds.

Gitar reads `.gitar/` from that repository's default branch on top of whatever the repository under review has of its own.

## Before you begin

* The configuration repository is available on the **Pro** and **Enterprise** plans. It is being rolled out per organization, so [contact support](mailto:support@gitar.ai?subject=Configuration%20repository) if you do not see the picker.
* You need the organization admin role.
* The repository has to be connected to Gitar already. AWS CodeCommit repositories are not selectable.

## What it holds

Skills today. Inherited [rules](/features/rules) and [review instructions](/configuration/repository-config#custom-review-instructions) are coming soon, so commit those into each repository for now.

## Set the configuration repository

<Steps>
  <Step title="Create or pick a repository">
    Any connected repository works. We suggest one named `.gitar`.
  </Step>

  <Step title="Commit a skill to it">
    ```
    .gitar/
      skills/
        migration-check/
          SKILL.md
    ```

    See [Writing a skill](/integrations/skills#writing-a-skill) for the frontmatter and an example body. Push to the default branch.
  </Step>

  <Step title="Name it in settings">
    Go to **Settings -> Configuration**. At the foot of the **Repositories** card, next to **Configuration repository**, select **Choose** and pick the repository.
  </Step>

  <Step title="Confirm what Gitar found">
    Saving reads the repository and lists the skills it found. The summary line reads like `acme/.gitar · 3 skills inherited by 6 repositories`.
  </Step>
</Steps>

Select **Clear** to stop inheriting.

## Where Gitar looks for skills

Five directories, in this order:

```
your-config-repo/
  .gitar/skills/<name>/SKILL.md
  .claude/skills/<name>/SKILL.md
  .github/skills/<name>/SKILL.md
  skills/<name>/SKILL.md                     # marketplace layout
  plugins/<plugin>/skills/<name>/SKILL.md    # marketplace layout
```

The first three are the same directories Gitar reads in any repository. See [Where skills live](/integrations/skills#where-skills-live) for the precedence rule.

The last two are the Claude Code and Copilot marketplace layouts, read only in the configuration repository, so a marketplace repository works as-is.

A repository's own copy wins. Commit a skill under `.gitar/skills/` with the same `name` as an inherited one and the local version is what runs.

## When changes take effect

A push to the default branch can take up to 15 minutes to reach the next run.

To test an edit before it lands, open a PR in the configuration repository itself. Gitar reviews that PR against the version on its branch rather than the version on the default branch.

<Warning>
  Anyone who can push to your configuration repository can change what every Gitar agent in your organization does. A skill body is instructions the agent follows, and a skill directory can carry scripts the agent runs.

  Protect its default branch the way you protect CI configuration: require review, and restrict who can merge.
</Warning>

## Troubleshooting

| The card says                            | Cause                                                         | Fix                                                                             |
| ---------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| A repository name in red, "disconnected" | The repository was disconnected from Gitar after it was named | Reconnect it, or name another repository                                        |
| "could not be read", with a reason       | Gitar could not fetch the repository                          | Pick the repository again to force a fresh read. Contact support if it persists |
| "no skills yet"                          | Nothing under any of the five directories                     | Add `.gitar/skills/<name>/SKILL.md` and push                                    |

Every failure is reported on the card rather than failing a run.

### An inherited skill never runs

Check the repository under review for a skill of the same `name`, which takes precedence. Then check the name against the slugs Gitar reserves for [integrations](/integrations/custom-integrations), such as `jira`, `linear`, and `slack`, plus `confluence`, `notion`, and `snyk`, which are reserved even though Gitar no longer ships them. A skill sharing one of those names is dropped, whether or not your organization has that integration turned on.

After that, see [Why is my skill not being used?](/integrations/skills#why-is-my-skill-not-being-used).