Add pyrig - #3282
Open
Winipedia wants to merge 2 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Adds pyrig to the Awesome Python catalog under CLI Tools → Productivity Tools, expanding the list of CLI-based productivity utilities with an opinionated Python project scaffolding/synchronization tool.
Changes:
- Added a new README entry for
pyrigunder “Productivity Tools”.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
daltino
reviewed
Aug 11, 2026
daltino
left a comment
There was a problem hiding this comment.
Thanks for working on this! The changes look neat and well-structured.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Project
pyrig
Checklist
Add project-name- [project-name](url) - Description ending with period.Why This Project Is Awesome
Which criterion does it meet? (pick one)
Explain:
pyrig scaffolds a complete, fully configured, and working Python project with a single command — dependency management, linting, type checking, testing, pre-commit hooks, CI/CD, and docs all wired up and functional from the start. Unlike a one-time generator, it stays involved after setup: running
pyrig synckeeps a project's tooling and structure current as pyrig itself evolves. It's built around a strict philosophy of shipping one opinionated, batteries-included default per concern rather than exposing a grid of configurable options, which keeps setup and maintenance genuinely simple rather than just configurable. However at the same time it offers full customization via a plugin system based on subclasses where you can adjust behavior and settings via overriding methods in a subclass.How It Differs
If similar entries exist, what makes this one unique?
cookiecutterandcopierrender a project template once at creation time — after that, the generated project is on its own. pyrig instead keeps ownership of a project's tooling and configuration over its lifetime:pyrig syncre-applies and updates the scaffolding as the project and pyrig itself evolve, rather than leaving you to manually maintain what was templated. It also goes further than templating alone, wiring up CI/CD, testing infrastructure, and dependency/version management as part of the same opinionated system, instead of a config file you customize yourself.