learn

Estrellas0

Forks0

Actualizado15 de junio de 2026 a las 18:21

Capture durable lessons from the current session — corrections, gotchas, decisions, term definitions — into kern and the project glossary. Use after a user correction, a surprising failure, or at the end of non-trivial work.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

yesitsfebreeze

yesitsfebreeze/machine

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

name	learn
description	Capture durable lessons from the current session — corrections, gotchas, decisions, term definitions — into kern and the project glossary. Use after a user correction, a surprising failure, or at the end of non-trivial work.

Learn — lesson capture

Follow references/learn.md.

Más de este repositorio

mismo repositorio

report

yesitsfebreeze/machine

File a machine self-diagnostic report as a tagged GitHub issue. When a tool, daemon, hook, skill, or agent hangs, errors, returns garbage, or behaves wrong, open a `machine-report`-labeled issue on the machine plugin repo so every plugin user's reports funnel to the maintainer. Requires `gh` logged in. Write-side only — it logs, it does not fix. Trigger: "/report", "report a problem", "this tool is broken", "file a machine report", "log this hang/error/hiccup".

2026-06-170

resolve

yesitsfebreeze/machine

Consume the machine self-diagnostic backlog. Lists the open `machine-report` GitHub issues on the machine repo, ranks them by severity then age, fixes the single highest-priority one at its root cause, verifies green, then closes that issue. The act side of /report (which only writes). Machine-repo-only skill — not shipped to other installs. Trigger: "/resolve", "resolve a report", "triage the reports", "fix the top report", "work the reports backlog".

2026-06-170

codex-review

yesitsfebreeze/machine

Second-AI review via the Codex CLI at the drill's single review point — the consolidated review of the finished diff, alongside the persona panel, before a landing is proposed. Advisory only: it returns notes and concerns for the driver and user to weigh, it never gates, blocks, merges, or edits. Skips cleanly when codex is not installed. Trigger via "/codex-review", "codex review", "second opinion from codex", or invoked by the drill skill.

2026-06-170

drill

yesitsfebreeze/machine

The drill — the orchestrator's default driver mode. Runs grill-first: the drill and the user refine a request one question at a time until the user calls it a valid plan. From there the job runs autonomously — a plan subagent writes a markdown brief, a miner implements it on a git-fs branch inside the orchestrator's worktree, and the gate iterates until the build is green — with one consolidated advisory review (personas + codex) at the end. The drill surfaces only to land the work into main, plus on any blocker it cannot resolve. The live roster lives in the hub (claims + board), not on disk. Trigger via "/drill", "drill mode", "orchestrator mode", "background this", "spawn an agent for this", "drive this".

2026-06-170

promote

yesitsfebreeze/machine

Promote crystallized brainstorm findings into board tickets. After a brainstorm (drill grill) settles one or more well-scoped features, this turns each into a card on the current cwd's board so the drill's plan step can iterate per ticket. The bridge between brainstorm and plan — it creates tickets, it does not plan or implement. Trigger: "/promote", "promote these", "promote to tickets", "make tickets", "turn findings into cards".

2026-06-170

questioneer

yesitsfebreeze/machine

Run the single ongoing chat that resolves the open plan and implementation questions parallel agents raise. Plan/implement agents post questions to mesh and wait; the questioneer aggregates them into one prioritized queue, presents each to you for a decision, and writes the answer back so the waiting agent proceeds. It routes decisions — it does not plan, implement, or dispatch. Trigger: "/questioneer", "questioneer", "answer the questions", "resolve open questions", "what are the agents blocked on".

2026-06-170