SkillFoxx

Makisuo Skills

Five skills for TypeScript: Effect 3 and 4 code review, service and layer rules, tech debt cleanup and a plan-to-merge PR loop

  • 79 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • The `david-workflow` skill opens PRs, waits for CI and checks deploys, so it works with your repository and services through `gh`
  • The `effect-review-v4` scripts read the project and run example checks
All reasons and checks

makisuo/skillsAuthor:Makisuo

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/makisuo-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The `david-workflow` skill opens PRs, waits for CI and checks deploys, so it works with your repository and services through `gh`
  • The `effect-review-v4` scripts read the project and run example checks

This is third-party code. Review the repository files before installing.

What it does

Makisuo Skills is a repository of five skills. The first three cover Effect-TS: `effect-best-practices` sets rules for services, errors, layers and atoms, `effect-review` runs a multi-agent review of branch changes against them, and `effect-review-v4` checks Effect 4 code for error propagation, resource ownership, cancellation, concurrency, schemas and tests and takes files, working changes, a branch diff or a whole repository. `zero-tech-debt` reworks a change as if the intended design existed from day one and deletes modes with no callers. `david-workflow` drives work end to end: a plan with verification, implementation, sub-agent review, a PR with evidence, green CI, a preview check and confirmation after merge.

Who it is for. TypeScript developers on Effect-TS and teams that want to take a feature from plan to merge on one procedure.

Good fit when

  • You write a service on Effect and ask the agent to watch layers, tagged errors and atoms
  • Before merge you need a branch review against Effect best practices with several reviewers
  • The project moved to Effect 4 and cancellation, resources and concurrency need checking
  • A patch grew compatibility modes and you want it reworked to the final design
  • A big feature is cut into verified phases and a PR stack through `gh stack`

Not a fit when

  • The project is not on Effect-TS: three of five skills are tied to its conventions
  • You have Effect 3: `effect-review` is for it, while `effect-review-v4` takes only version four
  • You do not use `gh` and Maple: the `david-workflow` loop relies on them
  • You need a ready linter instead of agent rules: the skills only steer review

Example request

Run an Effect v4 review of my branch changes: errors, resources, cancellation, concurrency and tests

Limitations

The repository has no README, so the description rests on SKILL.md files. The `effect-best-practices` skill treats the Effect Language Server as required and asks to install `@effect/language-service` and add it to `tsconfig.json`. For `effect-review-v4` the examples were verified against `effect` and `@effect/vitest` 4.0.0-rc.111, and APIs are checked against the installed version. `david-workflow` assumes `gh` and a PR stack via `gh stack`, a preview deploy and trace review in Maple, and without these tools some stages are skipped. `effect-review` targets the `main` branch.

How to disable. Delete the skill folders you do not need from the agent skills directory, for example `~/.claude/skills/effect-review-v4`. The skills leave no other traces.

FAQ

How do I install the Makisuo skills?

The repository has no README with an install command. Copy the folders you need, for example `effect-review-v4`, into the agent skills directory such as `~/.claude/skills/` and restart the client.

How does `effect-review` differ from `effect-review-v4`?

`effect-review` is for Effect 3 and runs a multi-agent branch review. `effect-review-v4` is for Effect 4, works with one agent by default and limits delegation to a total cap.

What does `effect-review-v4` check?

Error propagation, resource ownership, cancellation, concurrency, primitive choice, services and layers, schemas, atoms, observability and tests. It takes files, working changes, a branch diff or a repository audit.

What does `zero-tech-debt` do?

It reworks a change from the intended end state, looks for real callers and deletes modes, wrappers and fallbacks with none, rather than keeping them for compatibility.

What is `david-workflow` for?

For end-to-end work on a feature or fix: a phased plan, implementation, sub-agent review, a PR with evidence, CI and preview checks and confirmation after merge.

Discussion

No questions or reviews yet.

Skills

An Effect v4 skill for TypeScript: schemas, services and layers, config, retries, caches, streams, the HTTP client and tests with virtual time

SkillMinimal access355
Official

Official Effect skills that point the agent to the guide in node_modules and drive a project migration from version 3 to 4.

SkillExtended access115

Dillon Mulroy's personal skill set: strict TypeScript, Cloudflare Workers architecture, Effect services and technical specs

SkillMinimal access433

Twenty skills for reading unfamiliar code, reviewing documents and commits, translating Markdown and OpenSpec-driven development

SkillExtended access92

Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync

SkillExtended access1.6K

Over 200 skills by stack and practice: React, Next.js, Rails, Rust, Python, debugging, TDD and UI review

SkillMinimal access225

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
Makisuo Skills (this card)no79
Effect-TS Skillsyes115another set of Effect-TS skills; here a separate Effect 4 review and the david-workflow end-to-end loop
Effect skillno355a single Effect skill; here five skills with two generations of review and tech debt cleanup

README in short

The repository has no README. The structure shows five skill folders, and `effect-review-v4` has examples, the `inspect-project.mjs` and `check-examples.mjs` scripts and a set of evals. Descriptions come from the SKILL.md frontmatter.

README badge

Original SKILL.md

---
name: effect-review-v4
description: >-
  Review Effect v4 code, including beta, RC, and release versions, for correct
  error propagation, resource ownership, cancellation, concurrency, primitive
  selection, services/layers, schemas, atoms, observability, and tests. Use for
  requests such as "effect v4 review", "review my Effect 4 changes", "check
  Effect patterns", or "audit the Effect codebase" when the project uses v4.
  Supports files, working changes, PR/branch diffs, and repository audits.
  Reviews with one agent by default; delegation has an explicit total limit.
  Verify APIs against the installed version. For Effect v3 use effect-review.
metadata:
  version: "4.0.1"
  examples-verified-with: "effect and @effect/vitest 4.0.0-rc.111"
---

# Effect v4 review

Review program behavior and the contracts it exposes. Prefer Effect primitives
when they remove custom cancellation, scheduling, resource, or coordination
logic. Explain the semantic benefit; counting Effect APIs is not a measure of
code quality.

Use this skill read-only unless the user also requests fixes. When asked to
review or improve this skill itself, inspect its instructions and examples;
do not launch a product-code audit.

Default to **one reviewer: the current agent, with zero subagents**, including
whole-repository audits. Follow the delegation and context limits in section 3.

## 1. Establish scope and ground truth

Read [version-grounding.md](references/version-grounding.md) and the applicable
repository instructions before making findings.

- Respect explicit files/directories, PRs, branches, and prior conversation.
  "My changes" normally means working changes when present; otherwise inspect
  the current branch's actual base. State inferred scope. Ask only if unresolved
  ambiguity would materially change the review.
- PR/branch: determine the actual base, inspect its merge-base diff and relevant
  callers. Working changes: include staged, unstaged, and relevant untracked
  files. An empty diff is not a command failure. Never silently review `HEAD~1`.
- Repo: discover first-party source, excluding generated/dependency/reference
  trees. `.context` is API evidence, not product code under review.
- Classify by contents and ownership, not extension alone. `index.ts`, config,

Report a problem