Ryan McDougall
Community@rpmcdougall · United States
Ryan McDougall maintains 14 developer skills spanning Godot engine testing, SQL query explanation, agile planning, code review, and GitHub issue management.
Agent Skills by Ryan McDougall
Showing 14 vetted skills indexed across 1 GitHub repositories.
rpmcdougallpre-merge-housekeeping
Bundles checkpoint, wiki, and memory documentation updates into one docs commit before PR merge.
rpmcdougallgodot-repl
Runs throwaway GDScript snippets headless against the Godot engine and returns printed output.
rpmcdougallcheckpoint
Generates and commits a dated session checkpoint markdown file on the current feature branch.
rpmcdougallagile-project-manager
Generates user stories, sprint plans, backlog priorities, and retro action items for agile teams.
rpmcdougallengine-tests
Runs headless Godot test suites and reports a compact pass/fail summary.
rpmcdougallv17-rule
Extract verbatim rules citations with page numbers from Turnip28 v17 and v18 PDFs.
rpmcdougallruleset-diff-audit
Audits Godot engine code against ruleset PDFs and flags hardcoded rule constants.
rpmcdougallfile-issue
Creates GitHub issues via gh CLI using a standardized body template.
rpmcdougallsenior-software-engineer
Adopts a senior engineer persona to review architecture, code quality, and production readiness.
rpmcdougallsql-explainer
Explains SQL queries through layered walkthroughs for Snowflake, Oracle, and Databricks dialects.
rpmcdougallcombat-dice-budget
Computes worst-case dice pools for melee, shooting, and return-fire combat engagements.
rpmcdougallengine-feature-scope
Produces a scoping document for new Godot engine mechanics before any code is written.
rpmcdougallpost-merge
Syncs main, deletes merged feature branches, and suggests the next issue after a PR merge.
rpmcdougalladversarial-code-reviewer
Reviews code adversarially to find bugs, security holes, race conditions, and silent failures.
Frequently Asked Questions About Ryan McDougall
FAQPage SchemaWhat tasks can I accomplish with rpmcdougall's skills?▼
You can run Godot engine tests, sanity-check GDScript snippets via a throwaway REPL, explain SQL queries, compute combat dice pools, scope engine features from GitHub issues, file templated issues, plan sprints and groom backlogs, get adversarial code reviews, and manage pre/post-merge branch housekeeping with checkpoint documentation.
Who are these skills designed for?▼
Game developers working on the turnipsim Godot project, software engineers seeking senior-level design guidance or hostile code review, data practitioners analyzing Snowflake/Oracle/Databricks queries, and project leads running agile ceremonies like sprint planning, retros, standups, and backlog estimation.
How do the Godot testing and REPL skills work at runtime?▼
The engine-tests skill detects the platform-specific Godot path and runs headless test suites, reporting pass/fail summaries. The godot-repl skill writes a temporary tests/scratch_*.gd file extending SceneTree, executes it headless, returns printed output plus exit code, then deletes the file.
What prerequisites do these skills require?▼
Godot skills require a Godot installation and the turnipsim repository with its tests/ and rules_export/ directories. The file-issue skill requires the GitHub CLI (gh). SQL explanation needs only a pasted query. Checkpoint and housekeeping skills expect the project's memory/ directory and fixed documentation templates.
How do the merge lifecycle skills fit together?▼
Pre-merge-housekeeping bundles checkpoint files, wiki updates, and MEMORY.md/CLAUDE.md staleness checks into one docs commit before a PR opens. Post-merge syncs main, deletes the merged branch after remote confirmation, then reads the latest checkpoint's Next pickup section to suggest the next issue.