Prepare an open source contribution to Superset, from forking the code and setting up local development to running checks and opening a pull request. Follow repository rules and include evidence that the change works.
Set up a Paradev (formerly Superset) open-source contribution, from forking and cloning paradevai/paradev through local dev setup and the repo's rules to a merge-ready PR. Use when the user wants to contribute to Paradev, fix a Paradev bug themselves, add a feature to Paradev, or prepare a PR against paradevai/paradev.
Run score Not tested
See how to installThis skill helps prepare a contribution to Superset, from setting up the development environment through opening a reviewable pull request. It guides you through forking and cloning the repository, creating a workspace for each change, configuring local services, and following the repository's contribution rules. It also runs static checks, type checks, and tests. For visible interface changes, it includes review evidence such as screenshots or recordings.
Use it if you want to fix a Superset bug, improve its documentation, or contribute a feature. Small changes can go directly to a pull request. For a new feature or a larger change, the workflow starts by opening an issue to discuss the approach.
The workflow uses gh, git, and Bun, and uses Bun as the only package manager. It checks GitHub authentication, though local environment setup itself does not require external credentials. Existing CONTRIBUTING.md, DEVELOPMENT.md, and AGENTS.md take priority. Pull requests should cover one change at a time, use a Conventional Commits title, and pass lint without warnings.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Take the user from "I want to fix/build X in Paradev" to a merge-ready PR that follows the repo's rules. If the checked-out repo has CONTRIBUTING.md, DEVELOPMENT.md, or AGENTS.md, those files are authoritative; read them and prefer them over this summary.
gh auth status, then fork and clone: gh repo fork paradevai/paradev --clone (or add a fork remote to an existing clone)./.superset/setup.local.sh once (configures per-workspace ports, app identity, local services, and a seeded dev account; no external credentials needed), then bun run devAGENTS.md and follow it.main; one change per PR, so unrelated finds become a second PRbun run lint:fix, then verify bun run lint exits clean (CI fails on warnings too), bun run typecheck, bun run testfeat(desktop): ..., fix(web): ...); PRs are squash-merged with the title as the commit subjectgh pr create against paradevai/paradev main, fill in the PR template honestly (what you ran, what you clicked, what's covered by tests), and report the PR URL back to the user.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify a UI change or reproduce a bug in the running desktop app using the Chrome DevTools Protocol (CDP), a browser debugging interface. Follow the real user journey and compare screenshots with measurements such as route, scroll position, and persisted state.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.