Git Signing
Sign a participant's local git commits and tags with their own SSH signing key in the agent sandbox, isolated per Nuphos participant. Use when someone asks for commits signed with their own key, or when a change needs a real git commit / git push (file modes, symlinks, submodules, several commits) that must be Verified.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Git Signing when an AI agent needs a reusable SKILL.md workflow for this job: Sign a participant's local git commits and tags with their own SSH signing key in the agent sandbox, isolated per Nuphos participant. Use when someone asks for commits signed with their own key, or when a change needs a real git commit / git push (file modes, symlinks, submodules, several commits) that must be Verified.
When not to use it
Skip Git Signing when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/git-signing # Save SKILL.md to ~/.claude/skills/git-signing/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/git-signing/SKILL.md. For a shared project, commit the folder at .claude/skills/git-signing/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Git Signing skill for this task: Use Git Signing when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# git-signing — commits signed with a participant's own key
The `github` skill's `createCommitOnBranch` flow already produces Verified commits, signed by GitHub (`web-flow`). Use this skill instead when a participant wants the signature to be **theirs**, or when the work needs a local `git commit` / `git push`, which is otherwise unsigned in the sandbox. It works with any forge that accepts SSH signing keys (GitHub, GitLab).
A session home is shared by every participant in the conversation. This skill therefore never puts an author or signing key in the shared git config; each participant's identity lives in its own directory and is used only through `git-as`.
## Rules
- **Identity follows the sender.** Use `git-as <sender-id>` only with the current message's server-authored `sender.id`. Never commit as one participant on another participant's request, and never pick an identity from the runtime account, display name or provider login. - **Set up only on the participant's own request**, with the name and the email they want on their commits. The email must be verified on their forge account, or the forge shows the signature as Unverified. - **No silent fallback.** If signing or `git-as` fails, stop and report it. Do not commit unsigned, switch identity, or use `createCommitOnBranch` instead without saying so. - **Push as the same person.** Before pushing, re-run the forge's setup for the current sender (for GitHub, their Personal Credential) so the push and the signature belong to the same account. - Follow the repository's own rules. Some require `createCommitOnBranch`, others a `Signed-off-by` trailer (`git-as <sender-id> commit -s` adds one from the same identity).
## Setup
```bash bash skills/git-signing/scripts/setup-signing.sh <sender-id> --name "<name>" --email "<email>" ```
It creates a dedicated, passphrase-less ed25519 key under `~/.config/nuphos-git-identities/<sender-id>/`, writes that participant's git config there, removes author and signing settings from the shared config and sets `user.useConfigOnly=true`, installs `~/.local/bin/git-as`, and signs and verifies a probe commit. Running it again keeps the existing key.
Show the participant the printed public key and ask them to add it on the forge as a **Signing Key** (GitHub: SSH and GPG keys → New SSH key → Key type "Signing Key"; an Authentication Key does not verify signatures). Agent tokens cannot register keys for them.
## Use
```bash git-as <sender-id> commit -m "fix: ..." git-as <sender-id> tag -s v1.2.3 -m "v1.2.3" git-as <sender-id> log --show-signature -1 ```
Plain `git commit` without `git-as` fails with `Author identity unknown`; that is the isolation working, not a misconfiguration.
## Limits
- The key exists only in this conversation's session home. A new conversation needs a new key, registered again. Old keys can be deleted from the forge afterwards. - Isolation between participants is enforced by these rules, not by the OS: every participant's files belong to the same sandbox user. That is why the key is signing-only and revocable. Deleting it on the forge revokes it. - Never copy a participant's personal or primary key into the sandbox, and never print the private key.
Intended uses
- Use Git Signing when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.