Team

People behind kprompt

kprompt is early-stage and open source. We ship in public, keep safety honest, and welcome contributors who care about operator workflows.

Team members

Open source

Become a contributor

kprompt is MIT licensed and built in public. You do not need permission to open an issue or send a PR — start small, keep safety in mind, and link your work to a clear problem.

CLI issuesWebsite issuesRead docs

Areas we need help with

No formal roadmap lock-in — these are high-value places to start.

  • Safety rules, risk scoring, and hard-deny coverage
  • New LLM providers and preset quality
  • Helm install/upgrade flows and deeper Kubernetes investigation chains
  • Docs accuracy — install, providers, CI JSON, and operator examples
  • E2E tests on kind (deploy, scale, rollback, explain, logs)
  • Website UX, accessibility, and content (blog, docs, team)

How to contribute

A typical flow from idea to merged PR.

  1. 01

    Find or file an issue

    Search existing issues first. For bugs and features, open one with context: what you expected, what happened, and your cluster/provider setup if relevant.

  2. 02

    Discuss before large changes

    Small fixes and docs can go straight to a PR. For new tools, safety behavior, or architecture shifts, comment on an issue so we align on scope before you invest days of work.

  3. 03

    Fork, branch, and keep it focused

    One concern per PR — easier to review and safer to merge. Match the style of the repo you are touching (Go in CLI, TypeScript in website).

  4. 04

    Test what you change

    Run go test ./... for CLI changes. For website changes, npm run build and npm run lint. Add or update tests when behavior changes.

  5. 05

    Open a PR with context

    Explain why the change matters, link the issue, and call out anything operators should know (flags, safety, breaking behavior). No secrets, kubeconfigs, or API keys in commits.

CLI development

Clone and verify

git clone https://github.com/kprompt/kprompt.git
cd kprompt
go test ./...
go build -o bin/kprompt ./cmd/kprompt
./bin/kprompt version

Optional E2E

# Optional — requires Docker + kind
go test -tags=e2e ./test/e2e/ -count=1 -v -timeout 10m

Website development

Local preview at localhost:3000

git clone https://github.com/kprompt/kprompt-website.git
cd kprompt-website
npm install
npm run dev

Before opening a PR, run npm run build and npm run lint.

Pull request checklist

  • Linked issue or clear problem statement
  • Tests updated when behavior changes
  • Docs updated when user-facing behavior changes
  • No credentials, tokens, or private cluster details
  • Safety-sensitive paths called out in the PR description

Security & conduct

kprompt runs against real clusters with real credentials. Treat safety regressions seriously — call them out in PRs and add tests when you touch planner, safety, or executor paths.

Do not report security vulnerabilities in public issues. Use GitHub Security for responsible disclosure.

Participation should stay respectful and constructive. The project follows standard open-source community expectations — be direct, be kind, review plans before apply in your own testing too.

Ready to pick something up?

Browse open issues, comment to claim a task, or open a draft PR early if you want feedback on direction.

Browse CLI issueskprompt on GitHub