Awesome Reviewers expert instructions

domains / / the-pr-agent/pr-agent

Store Tokens in Secrets

Do not commit authentication credentials (e.g., GitHub personal access tokens, API keys, passwords) in versioned configuration files. Keep them in a dedicated secrets source such as `.secrets.toml` (or your secret manager), and ensure the committed config only contains placeholders/defaults.

raw .md Security Toml

Do not commit authentication credentials (e.g., GitHub personal access tokens, API keys, passwords) in versioned configuration files. Keep them in a dedicated secrets source such as .secrets.toml (or your secret manager), and ensure the committed config only contains placeholders/defaults.

Example (structure):

# configuration.toml (tracked)
[github]
deployment_type = "user"
user_token = "" # placeholder only
# .secrets.toml (not tracked / secured)
[github]
user_token = "ghp_..." # real PAT with minimal required scopes

Apply this by: (1) moving any *_token, api_key, password, or similar secret values to .secrets.toml; (2) adding/using ignore rules so secrets files are not committed; and (3) rotating any token that was accidentally checked in.