القائمة
This project uses flow for automation. When asked to build, test, run, deploy, lint, generate, or perform any dev task, check for a flow executable before falling back to raw shell commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | flow-context |
| description | This project uses flow for automation. When asked to build, test, run, deploy, lint, generate, or perform any dev task, check for a flow executable before falling back to raw shell commands. |
| user-invocable | false |
This repository uses flow for all development automation. The mcp__flow__* MCP tools are available.
When the user asks to build, test, deploy, lint, generate, or run anything:
mcp__flow__list_executables first — check whether a flow executable already handles the taskmcp__flow__execute with the matching verb and name — do not run a raw shell commandBash if no flow executable exists for the taskCommon refs: test unit, test e2e, lint, validate, generate, build binary
Use mcp__flow__list_executables to discover the full list and current names — don't assume.
Call mcp__flow__get_info at the start of a session or when you need schema URLs to author .flow files.
Scaffold a new Cobra CLI command following the project's patterns.
Add a new executable type to the flow runner (a new kind of automation block users can define in .flow files).
Run a pre-PR readiness check and report READY or NOT READY.
Run flow validate and fix any failures. Invoke after completing a feature or bug fix to confirm the codebase is clean before committing.