使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/erning/agent-skills --skill git-crypt開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
git-crypt
Use git-crypt for selected files that should remain readable in an unlocked work tree and encrypted in Git. Follow the user's chosen tool and file scope.
Task guidance
Read only the reference needed for the requested operation:
- New encryption rules, tracked plaintext, or checking stored contents:
- GPG access, symmetric-key export, or separate access groups:
- Locking, unlocking, errors, or encrypted patches:
references/troubleshooting.md.
For simple explanations, the constraints below may be enough. A setup request does not imply permission to grant access, rewrite history, or force-push.
Constraints
- Configure the encryption filter and matching
.gitattributesrules before
adding sensitive files to the index. Track .gitattributes; a separate earlier commit is optional. Verify encryption in the index before committing, and in the committed blob after a requested commit.
- Use
dir/**for recursive rules. Keep.gitattributes,.gitignore, and
.gitmodules unencrypted.
- Keep exported repository keys and private GPG keys outside the repository.
Do not print keys or secret file contents. Sensitive application files such as .env may be committed only after their stored form is verified as encrypted.
- Encrypting current files does not remove historical plaintext. If
credentials were exposed, advise rotation or revocation; history cleanup is a separate operation. A tracked file is not, by itself, evidence of a leak.
- Access cannot be revoked from someone who already has the key. Removing a
GPG grant does not invalidate their key or access to historical ciphertext.
- Filenames and other Git metadata remain visible. Encryption reveals file
lengths and equality; repository write access can be used to disable filters.
Complete the requested operation and verify its stored result. Report staged changes as staged, and do not claim that history or remote copies were cleaned without performing and checking that work.
Upstream reference
Use the installed version's git-crypt help for options and the upstream README for tool behavior and limitations.
