Jeff Lo
Community@sek788432
Jeff Lo maintains a C++-centric engineering skill registry covering static analysis, modern C++20 style, thread safety, performance tuning, code review, and test-driven development.
Agent Skills by Jeff Lo
Showing 22 vetted skills indexed across 1 GitHub repositories.
sek788432research
Investigate questions against primary sources and write cited findings to a Markdown file.
sek788432domain-modeling
Build and maintain a project domain glossary and living decision records.
sek788432cpp-static-analysis
Runs and interprets clang-tidy, scan-build, cppcheck, IWYU, and sanitizer checks for C++ code.
sek788432writing-great-skills
Provides vocabulary and principles for writing predictable AI agent skills.
sek788432cpp-performance
Detect and fix C++ performance smells in hot loops, containers, allocations, and synchronization.
sek788432diagnosing-bugs
Diagnose hard bugs and performance regressions through a phased feedback-loop workflow.
sek788432code-review
Reviews a change set against coding standards and its originating spec on two independent axes.
sek788432improve-codebase-architecture
Scan a codebase for module deepening opportunities and render findings as a self-contained HTML report.
sek788432to-spec
Synthesizes conversation context into a structured spec and publishes it to the project issue tracker.
sek788432codebase-design
Design deep modules with small interfaces, clean seams, and testable adapters.
sek788432prototype
Build throwaway C++ or Qt prototypes to answer design questions.
sek788432cpp-modern-style
Enforces modern C++20 style rules when writing or reviewing repository C++ code.
sek788432cpp-thread-safety
Enforces RAII ownership and thread-safe patterns in C++ code with sanitizer verification.
sek788432resolving-merge-conflicts
Resolve in-progress git merge and rebase conflicts by tracing original change intent.
sek788432review
Reviews branch changes, documentation, tests, and build checks against repository standards.
sek788432grill-with-docs
Interrogates a plan or design and updates decision records and glossary documentation.
sek788432implement
Execute approved implementation plans as dependency-ordered CI-green vertical slices.
sek788432teach
Create persistent teaching workspaces with HTML lessons, glossaries, and learning records.
sek788432tdd
Guides test-driven development using the red-green-refactor loop with behavior-focused tests.
sek788432grill-me
Runs a structured interview session to sharpen a plan or design.
sek788432grilling
Interviews the user one question at a time to stress-test plans and decisions.
sek788432cpp-oop-design
Enforces SOLID principles and design patterns for C++ module design and code review.
Frequently Asked Questions About Jeff Lo
FAQPage SchemaWhat tasks can I accomplish with Jeff Lo's skill registry?▼
You can run C++ static analysis stacks, enforce modern C++20 style, fix thread-safety and memory leaks, detect hot-path performance smells, conduct test-driven development, review diffs and branches, resolve merge conflicts, model domains, and convert conversations into published specs.
Who are these skills designed for?▼
C++ software engineers and maintainers working on performance-sensitive codebases, plus technical leads who need structured code review, architectural decision records, domain modeling, and design stress-testing through structured interview-driven planning sessions.
How do the C++ analysis skills work in practice?▼
The cpp-static-analysis skill orchestrates clang-format, clang-tidy, scan-build, cppcheck, include-what-you-use, and sanitizer-instrumented dev builds, interpreting warnings and configs like .clang-tidy before commits, pull requests, or merges.
What prerequisites do these skills require?▼
A C++ repository with the standard LLVM toolchain installed (clang-format, clang-tidy, scan-build), cppcheck, IWYU, sanitizer-enabled builds, and git for diff, branch, and merge-conflict operations. No external services or paid dependencies are indicated.
Do the skills cover testing and review before merging?▼
Yes. The tdd skill drives red-green-refactor cycles, while review and code-review examine committed, staged, unstaged, and untracked changes across Standards and Spec axes, verifying test intent, behavioral coverage, and documentation alignment before handoff.