Blog
Make your first contribution to SleekVoice
How to open a useful issue or pull request on SleekVoice, what GPL-3.0 asks of you, and which repository to use.
Published · Updated · 6 min read · Bharat Bhavnasi
On this page
- Read what is there before you write code
- What GPL-3.0 means for a patch
- Write an issue that can be acted on
- Open a small pull request
- What to contribute when you cannot build the app yet
- How review works
- Questions
- Do I need to sign a CLA?
- Can I contribute translations?
- Which repo gets a docs fix about the app’s shortcut?
A first contribution to SleekVoice is a change someone else can review: a bug report with enough detail to reproduce, a documentation fix, or a pull request that does one thing. The project is GPL-3.0 and says pull requests are welcome. It does not yet hand you a map of the app’s source, because on 20 November 2026 the application repository at github.com/SuperAgents-Dev/SleekVoice (opens in a new tab) had no published files. This post will not invent a file tree, a build command, or a “good first issue” label that is not on the tracker. It will tell you how to show up usefully anyway.
There are two repositories. The app is SuperAgents-Dev/SleekVoice. This website is SuperAgents-Dev/sleekvoice-website (opens in a new tab). Issues about dictation behavior belong on the app. Issues about these pages, the blog, or the install instructions belong on the website. Sending an app bug to the website tracker makes it invisible to the person looking at the app.
Read what is there before you write code
Open the app repository and read the current tree, the README if one exists, and the open issues. If the tree is still empty, your contribution is not a drive-by refactor of files you imagined. It is an issue that describes the behavior you want, or a pull request that adds something the maintainers can actually merge, such as a license file, a README that matches the website, or a note about how you installed a release build.
If a CONTRIBUTING file appears later, that file wins over this post. This post is the procedure for the case where that file is missing.
For the website, the stack is the one in its README: Next.js App Router, React, TypeScript, and Tailwind. Brand and profile links live in lib/site.ts. The footer renders enabled profiles from that file. Discord and X stay disabled until a URL exists, so a contribution that adds an empty social button is a bug, not a feature. Clone the website repository, install dependencies with npm install, and run npm run dev. npm run build is the check that the site still builds with no required environment variables. Analytics keys are optional. Do not commit a .env file. The gitignore already rejects them.
What GPL-3.0 means for a patch
The license text is at gnu.org/licenses/gpl-3.0 (opens in a new tab). In plain language: you can use, study, modify, and share the program. If you distribute a modified version to someone else, you have to give them the corresponding source under GPL-3.0 as well. A pull request to the project is you offering a change to the project. You should be comfortable with that change being GPL-3.0, because the project cannot take a patch under a conflicting “all rights reserved” footer.
This is not legal advice. If you are employed, your contract may say your employer owns what you write on a weeknight. Resolve that before you open the pull request. Do not paste a third-party snippet into the app unless its license is compatible and you say where it came from.
Whisper’s own code and weights are MIT, which is a different license from GPL-3.0. Using Whisper as SleekVoice describes is not the same as copying Whisper’s source into the repository. If a pull request vendors third-party source, name the license in the pull request so the reviewer does not have to guess.
Write an issue that can be acted on
A useful bug report has:
- macOS version, from About This Mac.
- Whether you installed with Homebrew or from a GitHub release, and which release if you know it.
- The app you were typing into.
- What you held, what you said, and what appeared. “Doesn’t work” is a mood. “TextEdit receives the sentence, Mail receives nothing, Accessibility is on” is a report.
- Whether the Mac was offline, if you were testing the local claim.
- What you already tried from the docs: microphone permission, Accessibility, cursor in a text field, shortcut conflict.
Do not attach someone else’s audio. Do not attach a recording of a meeting. A sentence you are willing to make public is enough. Do not include API keys, cookies, or the contents of a password field you dictated by mistake. If you already did, say so in the issue and rotate the secret. The issue tracker is public.
Feature requests should describe the job, not a guessed implementation. “I want the dictionary to import a line-separated text file” is reviewable. “Add a neural rescoring head” is not a first contribution unless you are also bringing a design the repository can hold.
Open a small pull request
For the website:
- Fork, or branch if you have access.
- Change one thing. A broken link, a wrong description, a docs step that does not match macOS, a contrast bug.
- Run
npm run build. - Open the pull request against the repository’s default branch. Say what changed and how you checked it. Screenshots help for visual changes. They do not replace the build.
For the app, once source exists:
- Read the build instructions in the repo. If they are missing, ask in an issue before you invent a scheme and send a 2,000-line diff.
- Keep the patch smaller than the problem. A drive-by rename of every type in the project will not be reviewed.
- Say how you ran it, on which macOS version.
- Do not add telemetry, a new network call, or a third-party SDK without explaining why local transcription still holds. The project’s public claim is that voice stays on the Mac. A pull request that uploads audio for “better accuracy” is a product change, not a cleanup. Discuss it first.
Commit messages should say what the change is. “fix” is not a message. “Document the Microphone pane in the setup guide” is.
What to contribute when you cannot build the app yet
You can still:
- Follow the install steps on a Mac and report where they diverge from the docs, including a missing Homebrew cask.
- Correct a factual slip on the website, especially anything about Wispr Flow that is not linked to a Wispr page.
- Add a test or a docs page to the website that fails the build if a required frontmatter field disappears.
- File the issue you wish a “good first issue” label already described, and include the acceptance check: what the app or the site should do when the change is done.
You should not:
- Open a pull request that adds a fake download counter, a star badge that calls the GitHub API and displays a number we then quote as a claim, or a testimonial.
- Add an MCP server, a plugin manifest, or an API route that does not implement a real API. The site is a marketing site. Pretending it is a platform makes agents and people trust a door that does not open.
- Commit secrets,
.envfiles, or a Google Analytics ID. The measurement ID is an environment variable in Vercel. The site renders no tag when it is unset.
How review works
The project is pull-request driven. That means a change lands when it is merged, not when it is posted on a social network. Be ready to answer questions. If a reviewer asks you to split a pull request, split it. If they ask you to drop a claim you cannot source, drop it. Silence for a while is not rejection. The repository may have one maintainer and a day job. Polite pings are fine. Demands are not.
Email hello@sleekvoice.app if you cannot use GitHub. Include the same reproduction detail you would have put in an issue. Security reports for this website use that address as well. security.txt says so.
Questions
Do I need to sign a CLA?
The project has not published a contributor license agreement. Do not let a third-party bot add one. If a CLA appears in the repository later, read it before you contribute again.
Can I contribute translations?
Only if you are also willing to maintain them or the project has a place for them. A single translated README that drifts from the English docs is a second source of false instructions. Ask in an issue first.
Which repo gets a docs fix about the app’s shortcut?
If the shortcut is wrong on sleekvoice.app, patch the website. If the app’s own UI text is wrong, patch the app once its source is public. Link the two pull requests if both need to change.
- contributing
- open source
- GPL-3.0
Related reading
- Open-source alternatives to Wispr Flow
How to judge an open-source alternative to Wispr Flow, and what SleekVoice, Wispr’s own pages, and Apple Dictation actually say.
- Set up local voice typing on macOS with Whisper
Install SleekVoice, grant the macOS permissions voice typing needs, and use push-to-talk without sending speech to a SleekVoice server.