All authors
Claude Skills by gmickel
github.com/gmickel70 skills235 installs2,509 views
- Flow Next Tracker SyncProject a flow-next spec to Linear, GitHub, GitLab, or Jira and reconcile body, status, and comments. Use for tracker discovery, linking, create-first, push, pull, reconcile, comment, or unlink. Not /flow-next:sync, which is plan-sync.Votes: 0GitHub stars: 705
- Flow Next VisualRestate a spec, a task, a diff, or the current topic visually as a compact markdown digest. Use when asked to 'show me', 'explain this visually', 'restate that', 'digest the plan', 'walk me through the spec', 'walk me through the tasks', 'walk me through the diff', or when the output is too much text and a shape would land faster. Triggers on /flow-next:visual with an optional spec id, task id, git range, or free-form topic.Votes: 0GitHub stars: 705
- Flow Next PlanFixture plan skill for OpenCode command stubs.Votes: 0GitHub stars: 705
- Flow Next SetupFixture setup skill for OpenCode command stubs.Votes: 0GitHub stars: 705
- Flow Next RefineRefine a spec or task before building: one Q&A interview, optionally focused by a scope lens, or a read-only research pass over external docs. Use to refine requirements or read up on a new library.Votes: 0GitHub stars: 705
- Flow Next FlowConductor for whatever the user has - an idea or a request for a change, a spec or task id, a tracker issue, a branch or a path, a pasted bug report or console output, a how or why question about the code, something slow to speed up, a cleanup that keeps behaviour, a design fork to settle, or "what should I do next". Use when the user states any of these without naming a skill; --auto runs unattended.Votes: 0GitHub stars: 705
- Flow Next RefineRefine a spec, task, or spec file before building - one question pass for the decisions that would change what gets built, optionally focused by a free-text --scope lens (business, technical, qa, ...), or a read-only research pass (--scope=research) that resolves library versions, changed APIs, and gotchas from external docs into the spec. Use when a named product, authority, or costly-to-reverse technical decision is open, or when the spec names a library or API the repo does not already use...Votes: 0GitHub stars: 705
- Flow Next DepsShow spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.Votes: 0GitHub stars: 704
- Flow Next Export ContextExport RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.Votes: 0GitHub stars: 704
- Flow Next Impl ReviewJohn Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.Votes: 0GitHub stars: 704
- Flow Next Plan ReviewCarmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow specs or design docs. Triggers on /flow-next:plan-review.Votes: 0GitHub stars: 704
- Flow Next PlanCreate structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).Votes: 0GitHub stars: 704
- Flow Next PrimeComprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.Votes: 0GitHub stars: 704
- Flow Next SetupOptional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.Votes: 0GitHub stars: 704
- Flow Next SyncManually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.Votes: 0GitHub stars: 704
- Flow Next WorkExecute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).Votes: 0GitHub stars: 704
- Flow NextManage .flow/ tasks and specs. Triggers: 'show me my tasks', 'list specs', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.Votes: 0GitHub stars: 704
- managing-google-sheetsRead, write, and update Google Sheets data via CLI. Use when the user asks to read spreadsheet data, update cells, append rows, or work with Google Sheets. Triggers on mentions of spreadsheets, sheets, Google Sheets, tabular data in the cloud, or specific sheet names like "Projects" or "Tasks".Votes: 0GitHub stars: 67
- sheets-cliRead, write, and update Google Sheets data via CLI. Use when the user asks to read spreadsheet data, update cells, append rows, or work with Google Sheets. Triggers on mentions of spreadsheets, sheets, Google Sheets, tabular data in the cloud, or specific sheet names like "Projects" or "Tasks".Votes: 0GitHub stars: 67
- raindropManage Raindrop.io bookmarks, collections, tags, and highlights via API. Use when user mentions raindrop, bookmarks, saving links, organizing URLs, bookmark collections, or web highlights.Votes: 0GitHub stars: 16