Carter LaSalle
Community@carterlasalle
Carter LaSalle publishes skills for converting confirmed bugs into permanent static-analysis detectors and maintaining requirement-to-code traceability in TraceLayer-active repositories.
Agent Skills by Carter LaSalle
Showing 3 vetted skills indexed across 2 GitHub repositories.
carterlasallescc-system-context
Retrieve evidence-backed system context from SCC-indexed repositories before planning or editing code.
carterlasallebug-corpus
Converts confirmed bugs into permanent deterministic static detectors enforced in CI.
carterlasalletraceability
Maintains trace:v1 markers linking requirements, code, tests, and evidence in TraceLayer repositories.
Frequently Asked Questions About Carter LaSalle
FAQPage SchemaWhat tasks can I accomplish with Carter LaSalle's skills?▼
Two tasks: turn a confirmed bug into a permanent static detector (Semgrep, CodeQL, Pysa, or ast-grep) to find similar bugs and prevent regressions, and maintain requirement-to-code traceability using TraceLayer trace:v1 markers, .trace/ config, and the trace CLI during development.
Who should use the bug-corpus and traceability skills?▼
Software engineers fixing bugs who want permanent static-analysis detectors for a bug class, and developers working in TraceLayer-active repositories who implement specs, modify traced symbols, change requirements or ADRs, or review PRs with trace diagnostics.
How do I run the bug-corpus skill in practice?▼
Invoke it after a bug is found or fixed, or when a Semgrep/CodeQL/Pysa/ast-grep rule is requested. It runs via `uv run bugcorpus`, which generates a permanent static detector capturing the bug's root cause so similar bugs can be found elsewhere.
What are the prerequisites for the traceability skill?▼
The repository must be TraceLayer-active, meaning a .trace/ config directory is present or `trace init` has been run. In passive or unconfigured repositories the skill does nothing TraceLayer-specific unless the user explicitly activates TraceLayer.
When does the traceability skill apply during development?▼
It applies when implementing specs, issues, or plans; modifying code containing trace:v1 markers; changing requirements, PRDs, or ADRs with downstream traces; refactoring traced symbols; adding verification tests; or fixing trace verify failures. Prose edits unrelated to traced artifacts are excluded.