yarlson
UserCLI that turns requirements into committed code.
Categories
Indexed Skills (18)
lgtm-phase-review
lgtm severe local phase review pass. Use after implementation and validation for exactly one PLAN.md phase to run a thermo-nuclear maintainability audit, identify ambitious behavior-preserving simplifications, and fix all safe phase-scoped findings before commit.
lgtm-phase-validate
lgtm validation pass for exactly one PLAN.md phase. Use when lgtm asks Codex validate implemented phase in the same session, compare implementation to Goal, Steps, Validation, Web validation sections, fix scoped gaps, verify concrete checks.
lgtm-cli-control
lgtm local CLI/TUI control skill. Use only when a selected PLAN.md phase changes CLI/TUI behavior, terminal output, prompts, interrupts, hangs, resize behavior, or terminal demos and needs repeatable local evidence.
lgtm-context-map
lgtm context discovery skill. Use before implement or validate to find files, docs, commands, risks, unknowns, local patterns for selected PLAN.md phase.
lgtm-dependency-review
lgtm dependency and supply-chain review skill. Use when a selected phase changes dependencies, lockfiles, package manager config, generated files, CI security config, tool versions, or plugin/MCP/tool installation.
lgtm-docs-drift-review
lgtm documentation drift review skill. Use when implementation or validation may affect README, AGENTS.md, PLAN.md, phase-linked project docs, API docs, operational docs, or other repo-local documentation.
lgtm-final-review
lgtm final phase closeout skill. Use at end of review pass: confirm selected phase contract satisfied, summarize verification, flag out-of-scope follow-ups, no scope expansion.
lgtm-phase-commit
lgtm after-phase commit pass. Use after impl, validation, review for exactly one PLAN.md phase to stage all changes and create one local git commit without pushing.
lgtm-phase-implement
lgtm implementation pass for exactly one PLAN.md phase. Use when lgtm asks Codex to implement a selected phase. Reads PLAN.md, AGENTS.md, and phase-linked context docs, maps relevant files, implements only the selected phase, keeps changes surgical, and verifies before finishing.
lgtm-plan-create
lgtm planning skill. Use when lgtm start interactive Codex planning session to make final PLAN.md and, when missing, AGENTS.md from user brief + answers.
lgtm-plan-update
lgtm PLAN.md update skill. Use only when implementation or validation proves the selected PLAN.md phase has an incorrect order, missing validation gate, impossible instruction, or incomplete phase contract.
lgtm-refactor-plan
lgtm refactor plan skill. Use when selected PLAN.md phase be refactor, cleanup, migration, decomposition, rename, or behavior-preserving change. Build minimal safe edit sequence before code change.
lgtm-rollout-review
lgtm rollout + operational readiness review skill. Use for phases involving deployment, infra, runtime config, migrations, observability, production behavior, or operational failure modes.
lgtm-security-review
lgtm focused security review skill. Use when a selected phase touches auth, secrets, shell commands, file IO, network calls, user input, dependency changes, MCP/tool configuration, agent boundaries, or other security-sensitive surfaces.
lgtm-spec-update
lgtm spec update skill. Use only when implementing or validating the selected phase exposes a real product, architecture, or behavior-contract gap that belongs in PLAN.md or a phase-linked project doc.
lgtm-technical-spike
lgtm bounded technical spike skill. Use when a selected phase depends on unknown, unfamiliar, or version-sensitive framework, library, tool, runtime, or platform behavior. Produces implementation-relevant conclusions without drifting into broad research.
lgtm-test-gap-review
lgtm test and verification gap review skill. Use during validation to detect weak tests, missing behavior coverage, fake confidence, skipped checks, or verification that does not prove the selected PLAN.md phase works.
lgtm-ui-control
lgtm local UI control skill. Use only when a selected PLAN.md phase changes browser, Electron, or local UI behavior and needs screenshot, accessibility, trace, or browser-driven evidence.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.