Configure Proofline from chat
Use the configuration workflow in the hosted Proofline plugin for ChatGPT or Codex, or the CLI-connected configuration skill in Claude Code. Name the organization and target repository or environment, then ask to see the saved value before changing it. The connection acts with the approving administrator’s authority.
For an ordinary setting, inspect the current and proposed values before agreeing that the agent should apply the change. A sensitive proposal provides a link for an authorized person to decide in Proofline. If the setting changed while you were reading it, start from the newer value before making another proposal.
Adjust pull request automation#
- Give a busy pull request time to settle before review
- Sample automatic reviews across an organization
- Exclude marked generated files in one repository through chat
- Restrict a repository’s reviews by base branch
- Let maintainers request a review with a GitHub label
- Apply a GitHub label for changes in a directory
- Change how a repository chooses human reviewers
- Mark repository paths that run outside linked environments
- Adjust a repository’s post-merge processing
Maintain review instructions#
- Create a review rule for files owned by one team
- Narrow an existing review rule to one language
- Retire an obsolete review rule from chat
- Decide whether a learned preference should guide future reviews
- Give one environment a specific review focus
Manage scan and report schedules#
- Schedule repository scans for matching release tags
- Pause an automatic repository scan while keeping its settings
- Remove a repository revision scan schedule
- Schedule an environment risk scan with a credit budget
- Adjust which problem families an environment scan examines
- End a recurring environment risk scan
- Pause weekly reporting for one environment
Control knowledge and review costs#
- Set a repository’s codebase build credit limit
- Set the maximum credits for a new change plan version
- Stop new implementations of approved plans
- Change model selection for future repository reviews
- Propose a different organization review budget
Manage context and gates#
- Pin a connected document to a repository path from chat
- Withdraw an obsolete document pin without disconnecting its provider
- Remove the binding for a retired repository contract
- Change the blocking severity of a repository merge gate
- Revise the signals used to check an environment’s deployments
Prepare changes that need browser approval#
- Propose scan-ticket filing permission for one repository
- Withdraw a repository’s standing scan-ticket permission
- Pause automated issue enrichment for a repository
- Adjust how agent-authored pull requests are covered
- Propose a narrower set of reads on an AWS connection
- Request verification after an AWS role repair
- Verify a repaired Google Cloud evidence connection
- Change which CloudWatch alarms an environment watches
- Stop watching CloudWatch alarms for an environment
- Change the Slack channel for existing-problem notifications
- Remove a Slack destination for existing-problem notifications
- Review a proposed automatic credit top-up change
- Propose a monthly spending limit for an organization
- Retire a Cloud Build trigger’s deployment gate binding
- Revise the rule for automatic approval of small pull requests
- Review a change to repository history used for context
- Draft a customer role with a narrow set of capabilities
- Rename an AWS connection without changing its reader
- Record an unused Google Cloud evidence source
- Withdraw an unused-source declaration when a project starts using it