Tools for managing your GitHub repositories at scale — skills, a desktop app, a Renovate CLI, and a DevOps sync — consolidated in one place (full git history preserved).
| Path | What it is | From |
|---|---|---|
skills/ |
Claude Code skills for auditing, managing and improving repositories | Atypical-Consulting/GitHubSkills ★ |
automate/ |
A Tauri desktop app for automating GitHub workflows | Atypical-Consulting/GitHubAutomate |
repo-tools/ |
A Spectre CLI to manage Renovate configurations across repos, with caching and interactive multi-select | phmatray/GitHubRepoTools |
devhub-sync/ |
Synchronize repositories between Azure DevOps and GitHub via a Blazor Server UI | phmatray/DevHubSync |
- Four complementary tools — each solves a different repo-management chore
- Mixed stacks — Claude Code skills, TypeScript/Tauri, and .NET/C#
- One home — shared issues, discussions and history for all your GitHub tooling
Each tool is self-contained in its folder — open it and follow its own README.
git clone https://github.com/Atypical-Consulting/github-toolkit.git
cd github-toolkit/repo-tools # or skills / automate / devhub-syncThe 18 ghs-* skills ship as a Claude Code plugin. Install them — do not copy the files:
/plugin marketplace add Atypical-Consulting/github-toolkit
/plugin install github-skills@github-toolkitCloning the repo only makes the skills available while working inside skills/, because they
live in a project-scoped .claude/skills/ directory. Installing the plugin makes them available
everywhere, which is the point of a tool that operates on other repositories.
Copying them into ~/.claude/skills/ instead would work once and then rot: ~/.claude is not a
git repository, so a copy drifts from its source with nothing to signal it.
Each folder was merged with full git history preserved (git subtree). The
original repositories are archived and redirect here.
- .NET 10 · .NET 9
- MudBlazor
- Microsoft.TeamFoundationServer.Client
- Octokit
- LibGit2Sharp
- Microsoft.EntityFrameworkCore.Sqlite
- Microsoft.EntityFrameworkCore.Design
- Microsoft.EntityFrameworkCore.Tools
- Spectre.Console
Planned work and known limitations are tracked in the open issues. Contributions toward them are welcome.
MIT — see LICENSE.
Contributions are welcome. Open an issue first to discuss any significant change.
- Fork the repository and create your branch (
git checkout -b feat/my-feature) - Commit your changes (
git commit -m 'feat: ...') - Push the branch and open a Pull Request