Jason Crawford
Community@jasoncrawford · Boston
Founder and President, Roots of Progress Institute (rootsofprogress.org). Former software engineering manager and tech startup founder.
Agent Skills by Jason Crawford
Showing 7 vetted skills indexed across 1 GitHub repositories.
jasoncrawfordno-force-push-main
Prevents force-pushing to main and guides safe force-with-lease use on feature branches.
jasoncrawfordno-cherry-pick
Prevents git cherry-pick usage and redirects blocked work toward waiting on unmerged pull requests.
jasoncrawfordno-commit-to-main
Prevents direct git commits to main or master branches and enforces branch-based PR workflows.
jasoncrawfordsemver
Recommends patch, minor, or major version bumps after pull requests merge.
jasoncrawfordbug-investigation
Verifies bug root causes through reproduction before implementing fixes.
jasoncrawfordbranch-discipline
Enforces branch-based Git workflows with pull requests and CI gating for all changes.
jasoncrawfordtest-discipline
Enforces writing failing-then-passing tests for every bug fix and feature change.
Frequently Asked Questions About Jason Crawford
FAQPage SchemaWhat tasks can I accomplish using Jason Crawford's skills?▼
You can enforce safe Git practices: block force-pushes to protected branches, prevent direct commits to main, avoid cherry-picking between branches, decide semver bump levels after merges, verify bug root causes before fixing, and require tests for every code change.
Who should use these Git discipline skills?▼
Software engineers, engineering managers, and teams working in repositories with CI pipelines, pull requests, or shared protected branches. They are especially useful when multiple contributors or parallel agents edit the same codebase and history integrity matters.
When do these skills trigger during development?▼
Each skill activates contextually: before running git push --force, git cherry-pick, or git commit on main; after a PR merge when choosing a version bump; when investigating a reported bug; and whenever implementing any bug fix, feature, or code change.
What prerequisites are needed to use these skills?▼
You need a Git-based project, ideally one with CI or pull request workflows and protected branches such as main or master. The semver skill assumes a merged pull request, and test-discipline assumes an existing test suite whose tests must not be skipped or broken.