open-index/open-npm huggingface dataset:
npm package: @fslab/fslab-styles
Description: npm package for FsLab web styles
Author: Kevin Schneider
Latest version: 2.1.0

# fslab-styles

![](https://img.shields.io/npm/v/@fslab/fslab-styles)

npm package for FsLab web styles

as seen on https://fslab.org.

- Set background color and emphasis via mixins (e.g. `has-bg`) and predefined classes (e.g `has-bg-darkmagenta`)
- Use component styling for:
  - package cards (e.g. as seen on https://fslab.org/packages.html)
  - Main page text fields (as seen on https://fslab.org)

based on [bulma](https://bulma.io/), uses [prism.js](https://prismjs.com/download.html#themes=prism-twilight&languages=clike+fsharp) for syntax highlighting

## install

for node:

`npm install @fslab/fslab-styles`

or use via cdn: 

`<scrpt src="https://cdn.jsdelivr.net/npm/@fslab/fslab-styles"></script>`
npm package: @fslzrr/uwui
Description: Personal UI components library
Author: fslzrr
Latest version: 0.0.2-alpha

# uwui

> personal components library

[![NPM](https://img.shields.io/npm/v/uwui.svg)](https://www.npmjs.com/package/uwui) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save @fslzrr/uwui
```

## Usage

```tsx
import React, { Component } from "react";
import { Button } from "@fslzrr/uwui";

const MyComponent: React.FC = (props) => {
  return <Button>Click me!</Button>;
};

export default MyComponent;
```

## License

MIT © [fslzrr](https://github.com/fslzrr)
npm package: @fsmiamoto/reagent
Description: Reagent: MCP server for local code reviews with GitHub-style UI
Author: Flavio Miyamoto
Latest version: 0.0.15

# ReAgent 

> **Re**views for your **Agent**

## Why is this useful?

In the era of AI coding assistants, ensuring their output code is high quality is essential for maintaining a healthy codebase. 

This often requires providing detailed, line-specific feedback, just like you would with a human teammate's code.

But pointing to specific lines through chat is clunky, and setting up GitHub PRs for local work-in-progress is really overkill.

ReAgent tackles that by creating a lightweight MCP server that opens a familiar, GitHub-style review interface right in your browser to speed your feedback cycles.

![ReAgent Usage](./docs/usage.png)

![Plan Review](./docs/plan_review.png)

## Features

- Interactive browser-based code review UI
- Line-level comments with file tree navigation
- Approve or request changes workflow
- Git integration: review uncommitted changes, specific commits, or branch diffs
- Local file review: review arbitrary files

## Usage

1. Add it as an MCP server to your favorite agentic coding tool.

```json
{
  "mcpServers": {
    "reagent": {
      "command": "npx",
      "args": [
        "-y",
        "@fsmiamoto/reagent@latest",
        "mcp"
      ]
    }
  }
}
```

### Prompting

The recommended way to use ReAgent is to steer your agent whenever you want to create a review session.

```
> Let's plan a change to [...]. Write the plan as a markdown file on the plans/ directory and create a review session.
```

You can also add ReAgent instructions to your AGENTS.md (or any context file your agent loads) to enforce reviews automatically:

```
- You MUST create a review session using ReAgent and get approval before proceeding to implementation.
```

### Two-Step Workflow

ReAgent uses a two-step workflow to enable interactive browser-based code reviews:

1. **create_review**: Initiates a review session and returns a URL.
2. **get_review**: Retrieves the completed review results.

## CLI Usage

ReAgent also provides a command-line interface for creating and managing review sessions.

For advanced users, you can also use the CLI directly without MCP by teaching your agent to invoke the commands ([learn more](https://mariozechner.at/posts/2025-11-02-what-if-you-dont-need-mcp/)).

### Installation

Install ReAgent globally to use the CLI:

```bash
npm install -g @fsmiamoto/reagent
```

Verify installation:

```bash
reagent --version
```

Alternatively, use `npx` without installation:

```bash
npx @fsmiamoto/reagent review
```

### Creating a Review

The most common CLI workflow is creating a review of your code:

```bash
# This will review all the uncommitted changes in your Git repo.
reagent review --auto-start
```

The `--auto-start` flag automatically starts the server if it's not already running. 

By default, the review URL will open in your browser.

## License

MIT
npm package: @fsmspa/lib
Description: FSM Design System lib
Author: Manuel Moreno
Latest version: 1.4.6

**Edit a file, create a new file, and clone from Bitbucket in under 2 minutes**

When you're done, you can delete the content in this README and update the file with details for others getting started with your repository.

*We recommend that you open this README in another tab as you perform the tasks below. You can [watch our video](https://youtu.be/0ocf7u76WSo) for a full demo of all the steps in this tutorial. Open the video in a new tab to avoid leaving Bitbucket.*

---

## Edit a file

You’ll start by editing this README file to learn how to edit a file in Bitbucket.

1. Click **Source** on the left side.
2. Click the README.md link from the list of files.
3. Click the **Edit** button.
4. Delete the following text: *Delete this line to make a change to the README from Bitbucket.*
5. After making your change, click **Commit** and then **Commit** again in the dialog. The commit page will open and you’ll see the change you just made.
6. Go back to the **Source** page.

---

## Create a file

Next, you’ll add a new file to this repository.

1. Click the **New file** button at the top of the **Source** page.
2. Give the file a filename of **contributors.txt**.
3. Enter your name in the empty file space.
4. Click **Commit** and then **Commit** again in the dialog.
5. Go back to the **Source** page.

Before you move on, go ahead and explore the repository. You've already seen the **Source** page, but check out the **Commits**, **Branches**, and **Settings** pages.

---

## Clone a repository

Use these steps to clone from SourceTree, our client for using the repository command-line free. Cloning allows you to work on your files locally. If you don't yet have SourceTree, [download and install first](https://www.sourcetreeapp.com/). If you prefer to clone from the command line, see [Clone a repository](https://confluence.atlassian.com/x/4whODQ).

1. You’ll see the clone button under the **Source** heading. Click that button.
2. Now click **Check out in SourceTree**. You may need to create a SourceTree account or log in.
3. When you see the **Clone New** dialog in SourceTree, update the destination path and name if you’d like to and then click **Clone**.
4. Open the directory you just created to see your repository’s files.

Now that you're more familiar with your Bitbucket repository, go ahead and add a new file locally. You can [push your change back to Bitbucket with SourceTree](https://confluence.atlassian.com/x/iqyBMg), or you can [add, commit,](https://confluence.atlassian.com/x/8QhODQ) and [push from the command line](https://confluence.atlassian.com/x/NQ0zDQ).