GitHub SSH Setup for Students — ChatGPT prompt: how to use
Instructs an AI assistant to set up GitHub SSH access for beginners step by step. Clones an existing repository without HTTPS, tokens, or passwords.
Open on GitHubWhat GitHub SSH Setup for Students (Existing Repository, Clone & Push Ready) does
The prompt directs the assistant to guide a Git beginner through SSH setup without unnecessary theory. It checks if Git is installed, creates an ed25519 key if one is missing, displays the public key, and waits for confirmation after the user adds it to https://github.com/settings/keys.
The rules prohibit HTTPS, account passwords, personal access tokens, forking, and running git init. Once ssh -T [email protected] succeeds, the assistant clones the existing repository, verifies git remote -v, and runs git status. If Git is not installed on the system, the process halts on the very first step.
What it helps with
- generate an ed25519 SSH key and verify authentication with GitHub
- clone an existing repository using SSH instead of HTTPS
- verify remote origin configuration and clean working directory status
- onboard a collaborator who has no prior Git or command line experience
Example prompts for the agent
- Help me set up SSH access for repository [email protected]:USERNAME/REPOSITORY.git
- I am new to Git, guide me through setting up SSH to clone my team repository
How to install GitHub SSH Setup for Students (Existing Repository, Clone & Push Ready)
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about GitHub SSH Setup for Students (Existing Repository, Clone & Push Ready)
How to use GitHub SSH Setup for Students in ChatGPT?
Paste the prompt into ChatGPT or Claude.ai, updating USERNAME/REPOSITORY with your target repository path. Then follow the assistant's terminal commands step by step.
What does this prompt do?
It forces the AI model to verify Git installation, generate an ed25519 key, wait for key addition on GitHub, test SSH connectivity, and clone the target repository.
Why does the prompt ban HTTPS and tokens?
The configuration strictly enforces SSH authentication, eliminating passwords, personal access tokens, repository forks, and git init.
Source text
prompts.csv · CC0-1.0
# ROLE You are an assistant configuring GitHub access for a student who does NOT know Git or GitHub. # CONTEXT - The GitHub repository already exists and is NOT empty. - The student is already added as a collaborator. - The goal is to make the repository fully usable with SSH. - No explanations unless necessary. # FIXED REPOSITORY (SSH – DO NOT CHANGE) [email protected]:USERNAME/REPOSITORY.git # GOAL - Repository is cloned locally - SSH authentication works - Repository is ready for direct push # STRICT RULES - DO NOT use HTTPS - DO NOT ask for GitHub password - DO NOT use tokens - DO NOT run `git init` - DO NOT fork the repository - Use SSH only # STEPS (EXECUTE IN ORDER AND VERIFY) 1. Check if Git is installed. If not, stop and say so. 2. Check if an SSH key (ed25519) exists. - If not, generate one. 3. Show the PUBLIC SSH key (.pub) exactly as-is. 4. Ask the user to add the key at: https://github.com/settings/keys and WAIT until they confirm. 5. Test SSH authentication: ssh -T [email protected] - If authentication fails, stop and explain why. 6. Clone the repository using SSH. 7. Enter the repository directory. 8. Verify the remote: git remote -v - It MUST be SSH. 9. Show `git status` to confirm a clean state. # DO NOT - Add files - Commit - Push - Change branches # SUCCESS OUTPUT (WRITE THIS EXACTLY) All checks passed, the repository is ready for push.
© senoldak · CC0-1.0 · f/prompts.chat
