Guides writing and refactoring fp-go v2 code using Pipe, Flow, reader monad, and do-notation patterns.
npx skills add https://github.com/IBM/fp-go --skill fp-go-pipe-flow
Please help me install this Agent Skill. Skill: fp-go-pipe-flow Source: https://github.com/IBM/fp-go/tree/main/gen/v2/data/skills/fp-go-pipe-flow Command: npx skills add https://github.com/IBM/fp-go --skill fp-go-pipe-flow
Writing functional Go code with the fp-go v2 library is error-prone because its combinators are low-frequency in training data, leading to misremembered signatures, wrong import paths, and imperative habits leaking into pipelines. This Skill provides verified patterns for Pipe, Flow, the reader monad, do-notation, and lenses so generated code compiles and follows fp-go idioms.
Refactor my imperative Go function into fp-go v2 style using Pipe, the reader monad with context.Context, and do-notation, and generate a unit test for it.
High-intent search queries and answers about installing and using this skill.
Use F.PipeN when you already have a starting value to thread through N functions, and F.FlowN when building a reusable function to pass to Map, Chain, or TraverseArray. The numeric suffix matches the number of transformation steps, from Pipe1 up to Pipe26.
Start with R.Do[Env](initialStruct) inside a Pipe, then add fields with R.Bind(setter, kleisli) for dependent steps, R.ApS(setter, reader) for independent ones, and R.Let for pure derived values. Setters and kleisli arrows should be named functions, never inline lambdas.
Only use the reader monad when the computation genuinely needs an environment such as context.Context, config, or a database handle. For pure transformations with no external input, use Flow or Pipe directly without any reader wrapping.
All imports must come from github.com/IBM/fp-go/v2, never from the v1 path github.com/IBM/fp-go. Common aliases include F for function, R for reader, O for option, A for array, and L for optics/lens.
Call the returned reader with a concrete lightweight environment struct rather than mocking it, then assert results with assert.Equal. For pure Flow or Pipe functions, invoke the returned function with a concrete value; prefer table-driven tests for multiple input/output pairs.
GabeujinGenerate a complete Go MCP server project using the official go-sdk.
LuohaothuFix Go build errors and vet issues with minimal changes.
osoleveProvide API metadata and usage guidance for lattice subsystems.
vanducngSelect and pin Samber Go libraries with decision matrices and upgrade rules.
