ReSuggestor

Cursor skill for frontend performance optimization. Install with npm, then use /resuggestor in Cursor chat.

Install

Global (all workspaces)

npm install -g resuggestor

Installs the skill to ~/.cursor/skills/resuggestor/. Available in every Cursor workspace.

Project (single repo)

npm install resuggestor

Installs to .cursor/skills/resuggestor/ and project hooks for canvas auto-open.

The postinstall script copies skill files only (npm cannot show interactive prompts). You must run setup yourself:

npm install -g resuggestor
resuggestor configure

Or for a project:

npm install resuggestor
npx resuggestor configure

Verify installation:

resuggestor doctor

Then fully restart Cursor (quit and reopen — not just reload window). Type /resuggestor in chat.

Use in Cursor

Open any project in Cursor and type in chat:

/resuggestor

See the skill docs for modes: module analysis, uncommitted changes, branch diff, GitLab MR review, apply suggestions, create PR, and post MR comments.

Configure later

resuggestor configure           # MCP + GitLab
resuggestor configure mcp       # Chrome DevTools MCP only
resuggestor configure gitlab    # GitLab env only
resuggestor install             # Reinstall skill files

Chrome DevTools MCP

Runtime analysis uses the user-chrome-devtools MCP server. The installer can configure ~/.cursor/mcp.json for you, or set it up manually:

npm install -g chrome-devtools-mcp --registry=https://registry.npmjs.org/
which chrome-devtools-mcp

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "/usr/local/bin/chrome-devtools-mcp"
    }
  }
}

Restart Cursor after changing MCP config.

GitLab

Credentials are stored in the skill config file (not committed):

| Install type | Config path | |--------------|-------------| | Global | ~/.cursor/skills/resuggestor/config/gitlab.env | | Project | .cursor/skills/resuggestor/config/gitlab.env |

Run resuggestor configure gitlab and paste your repository URL (for example https://gitlab.com/mygroup/my-repo), or enter GITLAB_URL, GITLAB_OWNER, and GITLAB_REPO separately. You also need GITLAB_TOKEN.

Requirements

• Node.js 18+
• git — uncommitted / branch / MR flows
• Chrome DevTools MCP — optional, runtime analysis only
• GitLab token — optional, MR flows only
• jq — optional, for project hook scripts

Publish (maintainers)

npm login
npm publish

prepublishOnly blocks publish if gitlab.env with secrets is present in templates.

License

MIT