container/.claude/skills/configure-git-cli/SKILL.md
Configure Git CLI with GitHub authentication using environment variables (GITHUB_EMAIL, GITHUB_NAME, GITHUB_PAT)
npx skillsauth add thomasgauvin/claude-agent-sdk-in-cloudflare-containers configure-git-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill before performing git operations (clone, push, commit, etc.). Required by the codebase-fix-and-pr skill.
Required environment variables:
GITHUB_EMAIL: Email address for git commitsGITHUB_NAME: Name for git commitsGITHUB_PAT: GitHub Personal Access Token with repo and workflow scopesgit --version
git config --global user.email "${GITHUB_EMAIL}"
git config --global user.name "${GITHUB_NAME}"
Enable credential storage and preload GitHub credentials:
git config --global credential.helper store
cat <<EOF > ~/.git-credentials
https://${GITHUB_NAME}:${GITHUB_PAT}@github.com
EOF
chmod 600 ~/.git-credentials
git config user.email
git config user.name
git ls-remote https://github.com/test/test.git
All commands should succeed without prompting for credentials.
git --version succeedsgit config user.email and git config user.name return correct valuesgit ls-remote succeeds without prompting| Issue | Solution |
|-------|----------|
| Git not found | Install git using your system package manager |
| Authentication failed | Verify GITHUB_PAT is valid, not expired, and has repo scope |
| Permission denied | Check write permissions to home directory |
| Credentials not working | Run rm ~/.git-credentials and reconfigure |
tools
Apply code changes to a GitHub repository and automatically create a pull request. Takes user feedback or fix requirements, clones the repo, makes localized changes, commits to a new branch, and opens a PR via GitHub MCP.
development
Analyze a GitHub codebase to create comprehensive architecture documentation including ASCII diagrams, component relationships, data flow, hosting infrastructure, and file structure assessment.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------