configure-agent-pr-attestation

Configure PR attestation hooks for AI coding agents with cosign and auth.json.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill configure-agent-pr-attestation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-agent-pr-attestation
Source: https://github.com/harness/harness-skills/tree/main/skills/configure-agent-pr-attestation
Command: npx skills add https://github.com/harness/harness-skills --skill configure-agent-pr-attestation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sets up a PostToolUse hook that signs and uploads an in-toto attestation for each PR/MR created by an AI coding agent, ensuring verifiable provenance and tamper-evident records for code changes.

Core Features & Use Cases

  • Install harness-scs attestation hook and configure a claude attestor
  • Troubleshoot why attestation uploads fail and reconfigure existing hooks
  • Reconfigure an attestation hook for different SCMs, cosign keys, or Harness identity

Quick Start

Run the skill to generate and deploy the agent-pr-attestation hook for your project, then test by creating a PR with any supported SCM tool.

Frequently Asked Questions about configure-agent-pr-attestation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PR attestation for AI coding agents?

Automating PR attestation involves setting up a PostToolUse hook that signs and uploads an in-toto attestation for each PR, ensuring verifiable provenance and tamper-evident records for AI-generated code changes. This skill configures the entire pipeline end-to-end.

Does Claude Code PR signing work with GitHub and GitLab?

Yes, Claude Code PR signing works across supported SCM tools including Harness CLI, GitHub CLI, GitLab CLI, Bitbucket CLI, Azure DevOps CLI, and Gitea/Forgejo. The skill patches Claude Code settings to enable deterministic signing on PR events for these platforms.

What is needed to configure cosign key management for PR attestations?

Configuring cosign key management requires checking prerequisites, configuring auth.json, and managing cosign keys. This skill automates these steps to generate an agent-pr-attestation hook script that handles deterministic signing for your PR workflows.

How do I troubleshoot when attestation uploads fail?

Troubleshooting attestation upload failures involves reconfiguring existing hooks and verifying your harness-scs attestation setup. This skill can reconfigure the hook for different SCMs, cosign keys, or Harness identity to resolve upload errors.

What are the limitations of using in-toto attestations for AI code changes?

In-toto attestations provide tamper-evident records and verifiable provenance for PR events, but require proper cosign key management and auth.json configuration. You must ensure your supported SCM CLI environment meets the prerequisites before deploying the hook.