github-tokenInteract with GitHub using Personal Access Tokens. Secure, user-controlled access - no OAuth, no full account access. Clone, push, branch, PR, issues. Use when user wants to work with GitHub repos.
Install via ClawdBot CLI:
clawdbot install dannyshmueli/github-tokenInteract with GitHub using Personal Access Tokens. User controls access via PAT scopes.
User provides their PAT:
1. Create PAT at github.com/settings/tokens
2. Select scopes (repo for full, public_repo for public only)
3. Provide token to agentStore in TOOLS.md or pass via --token.
# List repos you have access to
python3 scripts/gh.py repos [--token TOKEN]
# Clone a repo
python3 scripts/gh.py clone owner/repo [--token TOKEN]
# Create branch
python3 scripts/gh.py branch <branch-name> [--repo owner/repo]
# Commit and push
python3 scripts/gh.py push "<message>" [--branch branch] [--repo owner/repo]
# Open a pull request
python3 scripts/gh.py pr "<title>" [--body "description"] [--base main] [--head branch]
# Create an issue
python3 scripts/gh.py issue "<title>" [--body "description"] [--repo owner/repo]
# View repo info
python3 scripts/gh.py info owner/repoAgent stores token in TOOLS.md under ### GitHub section. Never expose in logs or messages.
Generated Mar 1, 2026
Developers use this skill to automate repository tasks like cloning, branching, and creating pull requests for collaborative coding projects. It streamlines workflows by handling GitHub operations directly from an agent, reducing manual steps in version control.
Teams integrate this skill into CI/CD pipelines to push code changes, manage branches, and open issues automatically. It enables seamless deployment and monitoring by interacting with GitHub repositories without manual intervention.
Researchers use this skill to clone and manage code repositories for data analysis or simulation projects. It facilitates version control and issue tracking in collaborative academic settings, ensuring secure access via personal tokens.
Technical writers automate updates to GitHub-hosted documentation by pushing changes and creating issues for review. This skill helps maintain versioned content and streamline editorial workflows in documentation projects.
Freelancers leverage this skill to quickly set up and manage client repositories, handle branching for feature development, and create pull requests. It simplifies project management and enhances productivity with secure token-based access.
Offer this skill as part of a paid subscription for developers, providing automated GitHub management tools. Revenue comes from monthly fees for access to enhanced features like batch operations or analytics.
Integrate this skill into enterprise software solutions for companies needing secure GitHub automation. Revenue is generated through licensing fees and custom integration services for large-scale deployments.
Provide a free version with basic GitHub operations and charge for advanced features like multi-repo management or priority support. Revenue streams from premium upgrades and add-on services.
đŦ Integration Tip
Store tokens securely in TOOLS.md and use minimal scopes to follow least privilege principles, ensuring safe automation without exposing sensitive data.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.