Jeremy Lightsmith
Community@jeremylightsmith · Seattle, WA
Jeremy Lightsmith publishes disciplined software engineering skills covering test-driven development, systematic debugging, code review handling, and Relay repo onboarding.
Agent Skills by Jeremy Lightsmith
Showing 8 vetted skills indexed across 1 GitHub repositories.
jeremylightsmithtest-driven-development
Enforces red-green-refactor test-driven development workflow before writing implementation code.
jeremylightsmithsystematic-debugging
Diagnose bugs through four-phase root-cause investigation before proposing fixes.
jeremylightsmithrelay-onboard
Reconciles a repo's agents and flows against a Relay board until the doctor reports zero errors.
jeremylightsmithbrainstorm
Turns feature ideas into approved designs through structured clarifying dialogue.
jeremylightsmithreceiving-code-review
Guides verification and reasoned response to code review feedback before implementation.
jeremylightsmithwriting-skills
Guides creation and editing of reusable agent skill documentation with trigger-focused descriptions.
jeremylightsmithrelay-doctor
Diagnose mismatches between Relay flow definitions and repo-provided agents, skills, and commands.
jeremylightsmithverification-before-completion
Enforces running verification commands before claiming work is complete or passing.
Frequently Asked Questions About Jeremy Lightsmith
FAQPage SchemaWhat tasks can I accomplish with Jeremy Lightsmith's skills?▼
You can enforce test-driven development before writing implementation code, debug failures systematically before proposing fixes, brainstorm designs before planning, process code review feedback carefully, verify work before committing or opening PRs, author new skills, and onboard or diagnose Relay-wired repositories.
Who should use these skills?▼
Software engineers and developers who want disciplined engineering practices: TDD practitioners, developers handling code review feedback, anyone debugging test failures, and teams wiring repositories to Relay boards or authoring their own skills and commands.
How do the Relay onboarding and doctor skills work together?▼
Use relay-onboard when first wiring a repo to a Relay board to seed the default factory or adopt existing agents and skills. Then relay-doctor validates that flows match the repo's factory, looping until it reports zero errors after flow, agent, skill, or command changes.
When should the verification-before-completion skill be invoked?▼
Invoke it whenever you are about to claim work is complete, fixed, or passing, before expressing satisfaction, or prior to committing, pushing, opening a pull request, or moving to the next task. It ensures claims are verified rather than assumed.
What are the prerequisites for using these skills?▼
The manifest specifies no external dependencies or installations. Skills are invoked contextually: TDD before implementation, systematic-debugging before fixes, brainstorm before design work, and relay-onboard/relay-doctor when a repository needs Relay wiring or flow-factory alignment checks.