Skip to main content
julienlegoux
GitHub creator profile

julienlegoux

Repository-level view of 22 collected skills across 1 GitHub repositories.

skills collected
22
repositories
1
updated
Aug 14, 2026
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

setup
software-developers

Set up this machine for the lx skills — today the `external-reviewer` CLI the review skills hand their analysis pass to, by installing the binary, putting a provider credential in place through kern-link's `pi-ai login`, and assigning the light/standard/heavy…

Aug 14, 2026
create-issues
software-developers

Break one epic (docs/epics/epic-N-slug/EPIC_N.md) into PR-sized issues — one .md file each plus a real GitHub issue on the epic's milestone, linked as a native sub-issue of the epic's tracking issue. Use whenever the user wants an epic broken into tasks,…

Aug 14, 2026
define-change
software-developers

Brownfield planning for one feature or serious change to an existing app — audit the code's blast radius, decide how the change lands through a user-triaged ledger under docs/planning/changes/, and deliver an EPIC_N.md (with GitHub milestone + tracking issue)…

Aug 14, 2026
implement-epic
software-developers

Supervise the implementation of all remaining issues in an epic by delegating each one to an implement-issue subagent, watching CI, and merging green PRs into the integration branch until every issue is done. Use whenever the user wants an entire epic from…

Aug 14, 2026
implement-issue
software-developers

Implement a single issue from docs/epics/ (produced by create-issues) as one focused, test-first PR — reconcile merged PRs, branch, strict red-green TDD against the acceptance criteria, open the PR, keep the bundle and GitHub issue in sync. Use whenever the…

Aug 14, 2026
split-epics
software-developers

Split a planning document (typically docs/planning/SCOPE.md) into one folder per epic under docs/epics/ — each with an EPIC_N.md, a GitHub milestone, and a tracking issue — ready for create-issues. Use whenever the user wants a plan or scope turned into…

Aug 14, 2026
check-prerequisites
software-developers

Probe what the planning bundle depends on — tools, runtimes, services, accounts, secrets — before epics are cut, and write docs/planning/PREREQUISITES.md, which carries the gaps only the user can close and the register implement-epic gates on. Use when…

Aug 14, 2026
okf-lint
software-developers

Semantic linter for OKF knowledge bundles — finds what a mechanical validator can't see (contradictions, index/log drift, duplicate concepts, taxonomy inconsistencies, stale content) and writes a severity-ranked report without modifying the bundle. Use…

Aug 11, 2026
Showing 8 of 22 collected skills.
Showing 1 of 1 repositories
All repositories loaded