How to Contribute to DenchClaw Open Source

How to contribute to DenchClaw open source—from fixing bugs and writing docs to building skills, sharing use cases, and reviewing PRs on GitHub.

The Dench Team

March 26, 2026·7 min read

How to Contribute to DenchClaw Open Source

DenchClaw is MIT licensed and openly developed on GitHub. The team building it is small; the vision is large. Both are intentional. A small, focused team ships fast and keeps the codebase coherent. But the ecosystem — skills, integrations, documentation, use cases — gets richer with every contributor.

This guide covers every way to contribute to DenchClaw: code, skills, documentation, community support, bug reports, feature ideas, and just using it and sharing what you find.

Why Contribute?#

Before the how, the why.

DenchClaw is building toward a world where AI-powered relationship management runs locally, is open and auditable, costs nothing to use, and belongs to the people who depend on it. That's a harder goal to reach than "build a SaaS and sell it." It requires a community.

When you contribute:

Your code ships to every user
Your skill reaches every DenchClaw workspace that installs it
Your documentation helps someone get unstuck in 5 minutes instead of 5 hours
Your bug report prevents the same issue from affecting a hundred more people

And frankly: contributing to an active open source project backed by YC, with a real user base and genuine community traction, is worth it for career reasons too.

Contribution Paths#

1. Fix Bugs and Submit PRs#

This is the most direct contribution. The GitHub issue tracker at github.com/DenchHQ/denchclaw is where bugs get filed and prioritized.

Good first issues are labeled good-first-issue and are specifically chosen for new contributors — isolated problems with clear acceptance criteria that don't require deep framework knowledge.

The contribution workflow:

# Fork the repo on GitHub, then:
git clone https://github.com/YOUR_USERNAME/denchclaw
cd denchclaw
npm install
git checkout -b fix/issue-123-describe-fix
 
# Make your changes
# Write tests if applicable
# Test locally: npx denchclaw (uses your local build)
 
git add -A
git commit -m "fix: describe what you fixed (#123)"
git push origin fix/issue-123-describe-fix
# Open a PR on GitHub

PR standards:

One issue per PR
Clear commit message following conventional commits format
Tests for anything that could regress
Update CHANGELOG.md if relevant

2. Build and Publish Skills#

Skills are the ecosystem multiplier. A well-built skill that solves a real integration problem can be installed by hundreds of users without any changes to the core codebase.

What makes a good skill contribution:

Solves a real integration gap (Apollo enrichment, Typeform capture, Stripe sync, etc.)
Has clear documentation in SKILL.md
Works with the existing DenchClaw agent patterns
Handles errors gracefully (API rate limits, auth failures, missing data)
Includes example instructions the user can send to the agent

Publishing to clawhub.ai:

# Create your skill
mkdir ~/.openclaw-dench/workspace/skills/my-integration
# Write SKILL.md following the AgentSkills spec
 
# Test locally
# Publish via the clawhub CLI
npm install -g clawhub
clawhub publish ./skills/my-integration/

Skills published on clawhub.ai get discovered by the full DenchClaw community. High-quality skills get featured in the skill spotlight and recommended by the agent.

3. Write Documentation#

Documentation contributions are high-leverage and often overlooked. The DenchClaw docs at docs.openclaw.ai are sourced from the repo at docs/. If you've struggled with something and figured it out, that's exactly the documentation gap that needs filling.

Good documentation contributions:

Fill gaps in getting-started guides
Add real examples to existing reference docs
Document undocumented behaviors you discovered
Translate docs into other languages
Fix typos, broken links, outdated information

To contribute docs:

git checkout -b docs/add-webhook-setup-guide
# Edit markdown files in docs/
# Preview with your Markdown editor
git commit -m "docs: add webhook setup guide"
# Open PR

4. Report Bugs Well#

A well-written bug report is a contribution. A vague one wastes everyone's time.

A good bug report includes:

What you expected to happen
What actually happened
Steps to reproduce (specific, minimal, can be followed by someone who's never seen the issue)
DenchClaw version (npx denchclaw --version)
macOS / Node.js version
Relevant error output or logs (from ~/.openclaw-dench/logs/)
A minimal reproduction if possible

Use the bug report template on GitHub. Fill in every field.

5. Request Features Thoughtfully#

Feature requests shape the roadmap. To make them count:

Search first: Is this already requested? If so, +1 with a comment sharing your specific use case
Describe the problem, not the solution: "I need X feature" is less useful than "I'm trying to do Y and currently can't because Z"
Include your use case: The team prioritizes based on who's affected and how severely
Be concrete: Mock screenshots, JSON examples, and workflow descriptions help immensely

The best feature requests become issues, get labeled, get prioritized, and eventually ship. The pipeline from community request to shipped feature is short at DenchClaw — the team is small and the codebase is focused.

6. Answer Questions in Discord#

The Discord community at discord.com/invite/clawd is where users get help, share setups, and discuss the product. As a power user, you probably know things that would help newer users — share them.

Channels to watch:

#help — users stuck on setup or workflow questions
#showcase — people sharing their DenchClaw setups (comment, learn, inspire)
#feedback — product feedback discussion
#dev — technical discussions and skill development

Active community members who regularly help others often get early access to new features and direct communication with the team.

One of the most valuable contributions for the community is sharing how you use DenchClaw. The community spotlight series is built from real user stories.

Your workspace setup (objects, fields, views)
Automations you've built
Skills you've created
Unexpected use cases you've discovered

Post in Discord #showcase, write a thread on X, or email us at hello@dench.com. The best stories get featured in the blog and help other users learn faster.

8. Star the Repo#

It sounds small. It isn't.

GitHub stars directly influence discoverability — how often DenchClaw shows up in "trending" lists, in GitHub Explore, in discussions about AI tools. For a bootstrapped (YC-funded) startup, organic discovery from GitHub is real distribution.

→ github.com/DenchHQ/denchclaw

If DenchClaw has been useful to you, star the repo. It takes 2 seconds and actually helps.