mcpField
S
superset-contribute

superset-contribute

github.com/superset-shDevelopment7103 installsUpdated 14w ago
Repository

About superset-contribute

A contribution skill that guides developers from a proposed Superset change to a merge-ready pull request. It covers repository setup, change scope, validation commands, and PR requirements, while deferring to repository guidance files when present.

Key features

  1. 01Choose an issue or PR path by change scope
  2. 02Fork and set up a development workspace
  3. 03Use Bun for development and validation
  4. 04Run lint, typecheck, and tests
  5. 05Prepare a conventional-title pull request

Use cases

  1. 01Prepare a small Superset bug fix
  2. 02Develop a feature after agreeing on its approach
  3. 03Validate and submit a Superset contribution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/superset-sh/skills --skill superset-contribute

After installing, type/superset-contributein Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported