Eric-Lingren
- 30 skills
- 0 followers
- yesterday last updated
- ▌ Pick · eric-lingrenRank the next ticket to pick up from the current repo's issue tracker. Reads issue_tracker and pick_buckets from repo-policy.json, shows a "Which bucket?" menu, and prints a top-5 list with copy-paste start lines. Read-only, terminal output only. Use when the user types /pick.
- ▌ Relay · eric-lingrenChannel-agnostic egress orchestrator for reply tasks. Reads the task file produced by /pr-revise, determines the target channel for each reply task from reply_url, presents combined drafts for final HITL approval, then routes each approved draft to the appropriate channel adapter under agents/egress/. Use when dispatch-tasks routes the reply branch, or the user invokes /relay <task-file>.
- ▌ Retro · eric-lingrenGenerate sprint retro talking points (3 things that went well, 3 ideas to improve) from your current-cycle GitHub PRs and Linear tickets. Prints inline for saying out loud in a synchronous retro. Use when the user says /retro, "sprint retro", "retro talking points", or "what went well this sprint".
- ▌ CI Fix · eric-lingrenDiagnose and fix CircleCI pipeline failures on the current branch. Pulls failing job logs via CircleCI MCP, applies all code fixes, verifies locally for non-hook-covered steps, and auto-pushes via gxpush. One shot per invocation.
- ▌ Capture · eric-lingrenCapture an idea, fix or bug as a GitHub issue without breaking flow. Use when the user says "capture idea", "capture fix", "capture bug", "capture that", "file that issue", "document that idea", "capture flush", "capture review", "capture import", or invokes /capture. Optional type word; a bare `capture` asks what the idea is. Builds the issue, shows one compact plain-text preview, and files it in the background on y.
- ▌ Offload · eric-lingrenOffload a skill invocation to a remote cloud agent. Accepts a target skill name and optional input content; looks up the skill's model and effort from model-tiers.json; spawns an Agent with isolation: 'remote' and the resolved model; instructs the remote agent to run the target skill at the looked-up effort level and return the full output as text; then writes the result to docs/seeds/ (for seeds) or docs/tasks/ (for tasks).
- ▌ To Seed · eric-lingrenDistill the current conversation or grill session into a standardized JSON IR (seed) and save it to docs/seeds/. Use when user wants to capture decisions and context from a conversation before moving to /to-spec, /to-tasks, or /prototype.
- ▌ To Spec · eric-lingren bundleRender a seed .json file into an interactive HTML PRD and save it to docs/prd/. Use when user wants to create a PRD from a seed file with rich interactive output.
- ▌ To Tasks · eric-lingren bundleBreak a seed or PRD into independently-grabbable tasks using tracer-bullet vertical slices, then write a JSON task file to docs/tasks/. Use when user wants to convert a seed file or PRD into AI-ready tasks.
- ▌ Worktree · eric-lingrenResolve or create a git worktree for a branch, list worktrees, or remove a worktree. Delegates entirely to the ~/.dotfiles/.scripts/worktree engine — same logic as the `wt` shell alias. Use when the user types /worktree <branch>, /worktree ls, /worktree rm <branch>, or asks to open/switch to a worktree from inside a Claude session.
- ▌ Find Work · eric-lingren bundleList active worktrees (and their Linear URLs) powered by gxlist. Falls back to listing spike/*, feat/*, and fix/* branches when gxlist is unavailable. Use when user wants to find previous spikes, feature branches, fix branches, or in-progress research branches.
- ▌ Pr Revise · eric-lingrenPost-publish PR feedback ingestion skill. Harvests reviewer and bugbot comments from an already-published PR, runs provisional triage, applies mandatory diligence, presents an HITL confirmation gate, fires attribution-tracer for confirmed escapes, and stops at a seed (via /to-seed) whose provenance captures both the code fixes and the PR replies to post. Use when the user says "revise PR", "process PR feedback", "review my PR comments", or invokes /pr-revise.
- ▌ Prototype · eric-lingren bundleExplore ideas, hypotheses, and design options before committing to a PRD. Runs throwaway code (terminal or UI) on a local-only git branch, then collapses findings into docs/prototypes/<filename>.md. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
- ▌ Tldr Tech · eric-lingrenSummarize the following technical content across four outputs. Use simple markdown throughout — bullets, bold, short lines. No long prose blocks. Everything must be skimmable at a glance.
- ▌ Build Code · eric-lingrenExecute tasks from a tasks JSON file sequentially, one build-runner spawn per task. Handles branching, status updates, blocker detection, leaf/blocker failure policy, and deferred HITL tasks without halting independent work. Use when user wants to run AI tasks from a docs/tasks/ file.
- ▌ Investigate · eric-lingrenInvestigates a question, claim, external signal, or incident by routing it to the investigator orchestrator agent (Opus tier), which decomposes it into sub-claims, routes each to the appropriate source, and returns a schema-valid investigation-result with a unified verdict and merged evidence.
- ▌ Sprout Seed · eric-lingrenEnd-to-end unattended pipeline: converts a seed file into tasks, executes every AFK task via build-code, and returns a pr-code-review of the resulting diff — all without user interaction. Use when you want one command to go from seed to reviewed PR.
- ▌ To E2e Tasks · eric-lingrenAnalyze branch changes, discover critical user-facing workflows, grill the test plan, and generate a Playwright e2e tasks JSON file for build-code. Output is a tasks JSON plan, not implemented tests. Use when user wants to plan e2e coverage after implementing a feature.
- ▌ Dispatch Tasks · eric-lingrenOrchestrate a task file by partitioning items by task_type and running one branch per invocation. Routes code items to build-code (inline), reply items to relay (inline), and triage items to export-tasks (agent). Re-entrant — run once per branch until all items are done. Use when user wants to dispatch a mixed task file, route deferred triage items to destinations, or run one pass of the pipeline.
- ▌ Pr Code Review · eric-lingrenComprehensive code review of staged changes or a PR. Checks for bugs, security issues, performance, and adherence to project conventions. Use when user says "review my changes", "review this PR", "code review", or invokes /review.
- ▌ Register Skill · eric-lingrenRegister a new skill or agent into the shared infrastructure so tier-advisor, the weekly usage report, and sync-model-tiers never miss it. Invoke as /register-skill <name>. Covers both the skill registration path (tiered via model-tiers.json skills map) and the agent registration path (tiered via model-tiers.json agents map). This file is the canonical reference for the full registration chain.
- ▌ Tasks To Linear · eric-lingrenConvert a docs/tasks/ JSON file into Linear tickets, preserving blocked-by relationships and writing Linear URLs back to the JSON. Use when the user wants to push tasks to Linear, create Linear issues from a task file, or sync tasks to Linear.
- ▌ Clean Scaffolding · eric-lingren bundleArchive consumed doc scaffolding (seeds, PRDs, tasks, handoffs) in the current working tree. Bundles each fully-consumed lineage chain verbatim into docs/archive/. Leaves docs/adr/, docs/prototype/, docs/standups/, and docs/wizard/ untouched. Deletes browser-checks, task trace logs, and docs/visual-changes/<branch-slug>/ directories for branches whose PRs are merged — without archiving. Use when done with a workflow and ready to clear the clutter. Pass --force or -y to skip the confirmation prompt.
- ▌ Improve Component · eric-lingrenAnalyze React components or TypeScript/HTML files for reusability, modularity, and hygiene improvements. Separates business logic from presentation, enforces design system usage, and proposes focused refactors. Use when user wants to improve a specific component, clean up a file, or make code more modular.
- ▌ Cc Usage Analytics · eric-lingrenView and explore Claude Code usage analytics — model mix, estimated cost, request intent, weekly trend, and per-skill tier adherence across the office (cco) and home (cch) profiles. Use when the user wants to see usage stats, run the benchmark, view the weekly report, check if model spend/tiers are trending right, or invokes /cc-usage-analytics.
- ▌ Run Task Followups · eric-lingrenWizard-style interactive walkthrough of manual follow-up actions from a tasks JSON file. Guides user through each follow-up one at a time with concrete steps (exact URL, click, value), progress framing, and confirm gates on irreversible actions. Enriches steps with codebase context, offers help when stuck, and captures friction to improve shared runbooks. For steps that capture secrets or write .env / gh values, generates a bundled bash snippet so secrets never pass through chat. Use when user wants guided help completing manual follow-ups after build-code.
- ▌ Improve Skill Learnings · eric-lingrenApply captured learnings from unified-learnings.jsonl to their target skill, agent, process, or contract files. Shows a ranked table of targets, lets the user pick one or "run all" (offered when TOTAL ≤ 10). A picked target with ≤ 10 learnings also offers "run all" for that target. Validation is lazy — runs per-learning just before drafting, not upfront in batch. Run-all loops through every target and learning automatically with a y/n per diff. Covers all four improves_type values: skill, agent, process, contract.
- ▌ Improve Agent Benchmarks · eric-lingrenCheap iterative improvement of a shared agent. Runs the next stage for the chosen agent (contract, cases, iterate). Contract stage drafts a cited, history-validated contract.json with an Opus subagent, shows each check with its source, historical pass rate and real failing examples, and freezes it on approval. Use when the user invokes /improve-agent-benchmarks [agent-name].
- ▌ Improve Directory Structure · eric-lingren bundleBuild a dependency graph over a directory tree and surface reorganization opportunities (misplaced shared nodes, low-cohesion clusters, near-duplicate files) informed by domain vocabulary and ADR decisions. Grills each candidate against a curated litmus set, then hands off a verified reorg plan via to-seed. Never moves files or rewrites references directly. Use when the user wants to reorganize a directory, audit repo layout, find directory-structure smells, or asks "does this belong here".
- ▌ Improve Codebase Architecture · eric-lingren bundleFind deepening opportunities in a codebase, informed by domain vocabulary and ADR decisions loaded via the context-loader agent. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.