kata-setup-gpg-signing

Configure Git to sign commits and tags with a GPG key.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-setup-gpg-signing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-setup-gpg-signing
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-setup-gpg-signing
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-setup-gpg-signing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents your GitHub commits and tags from showing as unverified by ensuring your Git client is configured to sign them with a GPG key that matches your GitHub account.

Core Features & Use Cases

  • Create and manage a GPG signing key: Generates a strong key and identifies the key ID needed for Git configuration.
  • Configure Git for commit and tag signing: Sets the signing key and turns on automatic signing for commits and tags.
  • Verify signatures locally and on GitHub: Confirms correct configuration using signature display in logs and the Verified badge on GitHub.

Use case example: You want every commit you push to Guardia repositories to display a Verified status so collaborators and reviewers can trust the author identity.

Quick Start

Run the kata steps to generate a GPG key, set git config user.signingkey plus commit.gpgsign and tag.gpgSign, then verify by creating an empty test commit and checking its signature output.

Frequently Asked Questions about kata-setup-gpg-signing

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

FAQPage Schema
How do I configure Git to sign commits with a GPG key for GitHub?▼

To configure Git to sign commits with a GPG key, you generate an RSA key, set its ID in git config user.signingkey, enable commit.gpgsign, and export the public key to GitHub. This ensures your commits display a Verified status.

Why does GitHub show my commits as unverified?▼

GitHub shows commits as unverified when your Git client is not configured to sign them with a GPG key linked to your GitHub account. You must generate a GPG key, configure Git to use it, and upload the public key to GitHub.

How do I enable automatic GPG signing for Git tags?▼

To enable automatic GPG signing for Git tags, set your signing key ID in git config and enable the tag.gpgSign option. This ensures all created tags are signed locally before being pushed to GitHub.

Can I use GPG signing for Git on multiple machines?▼

Yes, GPG signing for Git applies to multi-machine setup workflows. You must import your existing GPG key onto the new machine and apply the same Git configuration settings to ensure pushes and release tagging remain verified.

How do I verify that my Git commit signature is valid?▼

To verify your Git commit signature is valid, run git log --show-signature to check the cryptographic output locally. Then push the commit and confirm the Verified badge appears next to the author identity on GitHub.

Do I need an RSA GPG key to display a verified status on GitHub?▼

Yes, generating or selecting an RSA GPG key is required to display a verified status on GitHub. The key ID must be wired into your Git configuration and the public key exported to your GitHub account to validate trusted authorship.