Jeffrey Girard
Community@jmgirard · Lawrence, KS, USA
Associate Professor of Psychology
Agent Skills by Jeffrey Girard
Showing 10 vetted skills indexed across 1 GitHub repositories.
jmgirardhotfix
Fix user-visible bugs in cairn-tracked repos with regression tests, gate-lite checks, and gated PR merges.
jmgirardmilestone
Audits cairn project tracking files and routes the next milestone action.
jmgirardcairn-init
Scaffolds, repairs, or migrates cairn milestone-tracking files in a git repository.
jmgirarddesign-interview
Elicits design facts and formalizes guiding principles into a repo's DESIGN.md.
jmgirardcairn-release
Prepares versioned releases by running the active toolchain profile's release walk with changelog consolidation.
jmgirardmilestone-brief
Escalates hard technical questions to Fable-level review via self-contained review briefs and ingests the resulting reports.
jmgirardcairn-triage
Triages roadmap candidates and known issues into dispositions applied in one docs-only commit.
jmgirardmilestone-plan
Plans scoped milestones with acceptance criteria and registers them in a project ROADMAP.
jmgirardmilestone-implement
Implements a planned milestone on its own git branch with tests-first tasks and checkpoint commits.
jmgirardmilestone-review
Verifies and merges finished milestones with fresh evidence, consistency gates, and independent code review.
Frequently Asked Questions About Jeffrey Girard
FAQPage SchemaWhat tasks can I accomplish with jmgirard's cairn skills?▼
You can initialize cairn tracking in a repo, plan and implement milestones with tests-first tasks, hotfix user-visible bugs with regression tests, triage roadmap candidates and known issues, prepare CRAN or generic releases, run design-elicitation interviews for DESIGN.md, and escalate hard questions via Review Briefs.
Who are the cairn skills designed for?▼
They target software maintainers and R package developers who manage repositories with structured milestone tracking. They suit engineers who want disciplined bug fixing, release preparation with CRAN submission checklists, backlog pruning, and documented design principles rather than ad-hoc project management.
How does the milestone lifecycle work in practice?▼
Run milestone-plan to scope work and register acceptance criteria in the ROADMAP, then milestone-implement to build it on its own branch with tests-first tasks and checkpoint commits. Finish with milestone-review, which verifies fresh evidence for every criterion, runs an independent code review, and merges on user approval.
Does cairn-release submit packages to CRAN automatically?▼
No, it never self-submits. For an r-package profile it runs the CRAN walk: version bump, NEWS update, checks, cran-comments, and a human submission checklist. A generic profile performs a version bump, changelog, and tag. You invoke it with a patch, minor, or major argument.
What prerequisites are needed to adopt the cairn system?▼
You need an existing git repository. The cairn-init skill scaffolds the cairn/ tracking files, adds a CLAUDE.md section, and sets ignore entries, or migrates an existing precursor tracking system. No other dependencies are stated in the skill manifest.