Reviews pull requests for fp-go v2 code against functional programming conventions and best practices.
npx skills add https://github.com/IBM/fp-go --skill fp-go-pr-review
Please help me install this Agent Skill. Skill: fp-go-pr-review Source: https://github.com/IBM/fp-go/tree/main/gen/v2/data/skills/fp-go-pr-review Command: npx skills add https://github.com/IBM/fp-go --skill fp-go-pr-review
Reviewing Go pull requests that use the fp-go library requires deep knowledge of functional programming conventions like data-last composition, point-free style, and monad selection. This Skill automates that review by checking changes against 16 concrete fp-go rules and producing a structured, severity-ranked report.
()), Result-over-Either usage, lens-based do-notation, Bind vs ApS semantics, and TraverseArray patterns.gh CLI.github.com/IBM/fp-go/v2. Run this Skill to get the diff, verify the branch compiles with go build and go vet, detect a missing IO execution and an inline lambda that should be point-free, then post a structured review comment.Review the current pull request branch for fp-go v2 best practices and post a severity-ranked summary comment on the GitHub PR.
High-intent search queries and answers about installing and using this skill.
Check out the PR branch, run git diff main...HEAD to get changes, then validate against fp-go rules: v2 import paths, data-last composition, point-free style, and proper monad usage. Confirm the branch compiles with go build and go vet before reviewing style.
fp-go v2 uses the import path github.com/IBM/fp-go/v2/... and requires Go 1.24+ for generic type alias support. V1 and v2 are incompatible, so mixing import paths causes compilation errors and is flagged as a Critical issue.
Use Result[A] when the error type is Go's standard error, since Result is defined as Either[error, A] and is more idiomatic. Reserve Either for custom error types like ValidationError where the left side carries domain-specific information.
IO values in fp-go are lazy functions, so IO[A] is func() A and must be called with trailing parentheses to execute. For ReaderIOResult, you need both the context argument and an extra call: pipeline(ctx)().
Use Bind when a step depends on accumulated state from previous steps, and ApS when steps are independent of each other. Using Bind for independent steps obscures intent, while ApS makes the independence explicit.
The review checks stylistic and structural conventions but cannot verify business logic correctness or runtime behavior. It relies on the branch compiling first, and findings still require human judgment for context-specific design decisions.
multigresGenerates a PR title and description from the branch diff and creates a draft pull request.
rickyanandaReviews GitHub pull requests and local diffs for security and quality issues.
erigontechRuns Erigon Go test suites with the race detector to find data races and concurrency bugs.
VIethoangnguyenleImplement monadic Option, Result, and Either types in Go.