superset-sh/skills

superset-contribute

Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR.

First seen Aug 5, 2026

Installation

$ npx skills add superset-sh/skills --skill superset-contribute

Summary

  • Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR.
  • Use when the user wants to contribute to Superset, fix a Superset bug themselves, or prepare a PR against superset-sh/superset.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from superset-sh/skills · top by installs.

npx skills add superset-sh/skills

Browse all from superset-sh/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE.md
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,472 B
  • docs SUMMARY.md 329 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 57 installs

SKILL.md

Contribute to Superset

Take the user from "I want to fix/build X in Superset" to a merge-ready PR that follows the repo's rules. If the checked-out repo has CONTRIBUTING.md / DEVELOPMENT.md / AGENTS.md, those files are authoritative — read them and prefer them over this summary.

1. Scope first

2. Set up

  1. gh auth status, then fork and clone: gh repo fork superset-sh/superset --clone (or add a fork remote to an existing clone)
  2. Best experience: add the clone as a project in the Superset app and create a workspace per change — contributions develop inside managed worktrees
  3. In the new workspace/worktree, run ./.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 dev
  4. Bun only — never npm/yarn/pnpm. Read the root AGENTS.md and follow it.

3. Make it merge-ready

  • Branch from main; one change per PR — unrelated finds become a second PR
  • Before pushing: bun run lint:fix, then verify bun run lint exits clean (CI fails on warnings too), bun run typecheck, bun run test
  • PR title must be a conventional commit (feat(desktop): ..., fix(web): ...) — PRs are squash-merged with the title as the commit subject
  • Include proof it works: screenshots or recordings for anything user-visible, before/after for fixes. The dev desktop app exposes CDP for clean captures — see "Capturing screenshots via CDP" in CONTRIBUTING.md
  • Check "Allow edits from maintainers" and link the issue for non-trivial changes

4. Open it

gh pr create against superset-sh/superset 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.