Set practical permissions

Prompt to try

/permissions

Create a branch and save all these changes into version control.

Make a pull request for me.

Check your work

Use /permissions, /sandbox, or accept-edits mode to reduce routine prompts while keeping review where it matters.

In the /permissions step, enable all git commands Bash(git:*) and GitHub command Bash(gh:*) for this project.

Confirm that this has worked, and merge it. You can then ask Claude to pull.

(Bonus: try having Claude resolve a merge conflict)

Narration

Listen or continue with the transcript

Auto-play audio on each slide

Transcript

Now let's practice using the /permissions command and integrating Claude with git.

Here's your exercise: First, run /permissions to configure git permissions. In the permissions interface, enable all git commands using Bash(git:*) and GitHub commands using Bash(gh:*) for this project.

Once you've set those permissions, ask Claude to create a branch, save all your changes into version control, and make a pull request for you.

This exercise demonstrates how Claude can handle your entire git workflow once you've granted the appropriate permissions. You'll see how Claude creates a branch, commits your changes with a proper commit message, and even opens a pull request using the GitHub CLI.

For extra protection, try /sandbox or accept-edits mode and notice how the workflow changes. The point is to reduce routine prompts without losing review where it matters.