- Skills
- 18
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 0
alejandro waumann 的 Skills 18
pr-review
Review a pull request against the team's checklist.
inner
Inside another skill, so never listed.
sql-helper
Write SQL for the warehouse.
foo
Out of scope (enterprise/plugins).
query-warehouse
Run read-only SQL against the warehouse.
catalog
Look up tables in the data catalog.
guide
Out of scope (docs).
haiku-writer
暂无简介
secret
In a hidden directory, so never listed.
lint
Lint the current change.
x
Out of scope (community/instructions).
code-foundry
Start here for anything about Code Foundry, the app this thread runs in. Use when asked what you can do, what's running, their work, this worktree's changes or PRs, version, model, effort, usage, cost, settings, plugins; to see or make a file, diff, page, HTML, chart or theme, a mockup or a recolour; a preference to remember; a skill, PR, reminder, a secret or a file you cannot read; or before acting in the app.
code-foundry-plugin
Build, debug and publish a Code Foundry plugin: a Go executable with a plugin.json manifest that adds commands, surfaces (tabs), thread flags, event subscriptions, session environment or its own Claude threads and terminals. Use for anything touching a plugin, plugin.json, pluginsdk, pluginsdk/ui or plugintest, for the code-foundry plugin dev, logs, surface or act commands, or for a plugin registry.
code-foundry-pages
Build an HTML or React page that reads Code Foundry live and acts on it through /cf/bridge.js: merge PRs, archive or start threads. Use when the user wants a page, dashboard, board, tracker, form, chart or tool; a checklist or to-do to tick off; to see what's running, what's going on or their work (threads, PRs: not the Mac's processes); something as UI or a mockup; or a page of yours misbehaves.
code-foundry-orchestrate
Run several pieces of work in parallel as Code Foundry threads, each in its own worktree and branch. Use when the user asks for more than one change on separate branches or PRs, to do things in parallel, to split work up, or to use subagents, helpers or agents for work that edits files; also to create, read, wait on, wake or manage other threads. Wait for them, collect their reports, archive, clean up. For a single change you are asked to make yourself, do it in your own checkout. Native subagents only for read-only research.
code-foundry-help
Answer how-to questions about Code Foundry, the app this thread runs in: projects, workspaces, threads, worktrees, settings, keybindings, PRs, actions. Use when the user asks how to do something or how it works, wants a setting changed, states a standing preference about the app or how you work in it (remember it), asks to see something, or before you show something in a tab beside you.
code-foundry-ember
Ember's working loop: turning the user's request into tasks on the board, one worker thread per task, following them through wakes, checking their reports and telling the user. Use for every request the user makes of Ember and for every wake Ember receives.
drive-app
Drive the Code Foundry GUI in a headless WebKit browser with `playwright cli` to check a change while making it, explore a flow, or render a sketch inside the real app. Use instead of one-off Playwright scripts. Not for PR screenshots (the SHOTS-gated e2e specs make those) and never for public web pages.