# Feedback

Collect and submit feedback about Paradev (formerly Superset) (bug reports, feature...

- Repository: https://github.com/ParadevAI/Paradev (15823 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ParadevAI/Paradev --skill feedback -g -a claude-code -y`
Codex: `npx skills add ParadevAI/Paradev --skill feedback -g -a codex -y`
Cursor: `npx skills add ParadevAI/Paradev --skill feedback -g -a cursor -y`
Gemini CLI: `npx skills add ParadevAI/Paradev --skill feedback -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ParadevAI/Paradev`

## Description

Collect and submit feedback about Paradev (formerly Superset) (bug reports, feature requests, or general feedback) privately to the Paradev team or as a public GitHub issue. Use when the user wants to report a Paradev bug, request a feature, or send feedback about Paradev.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Paradev Feedback

`paradev` is an alias for the `superset` CLI: every `superset` command here also runs as `paradev`.

Check Paradev's documentation for an existing answer first. When feedback still needs reporting, turn it into a short, scannable report and submit it where the user chooses. Treat whatever they wrote after the command as the seed.

The reader is a Paradev engineer triaging dozens of reports. They should get the point from the title, the full picture from the summary bullets, and only read further when they need detail. Cut everything that doesn't help them reproduce or decide.

## 0. Is this a follow-up?

Every private submission CCs the reporter, so they already have a copy in their inbox with a subject starting `[Feedback: ...]`. A reply to that email lands on the same thread; a new submission opens a new one and the team has to reconcile them by hand.

If the seed reads like a continuation ("follow-up", "again", "still happening", "update on", "retraction", "root cause", "I already sent", "third time"), or the user filed something on this topic earlier in the session, ask whether they already sent a report about it. If they did, tell them to reply to that email with the new information and stop here. Only file fresh when they confirm it's a different issue.

Never title a report "Follow-up:", "ROOT CAUSE:", or "RETRACTION"; those belong in a reply.

### Check the knowledge base before gathering report details

Search the Paradev documentation for the user's question, symptom, or requested capability. Use `docs_search` with relevant keywords, then `docs_read` on promising results when the Paradev docs MCP tools are available. Otherwise fetch `https://docs.paradev.com/llms.txt` and read the relevant linked pages, or use web search restricted to `docs.paradev.com`. Use generic product terms and error messages; keep private paths, account details, and logs out of search queries.

The rest: https://github.com/ParadevAI/Paradev/blob/HEAD/plugins/superset/skills/feedback/SKILL.md