-
Notifications
You must be signed in to change notification settings - Fork 0
Contributing
Josemalyson Oliveira edited this page Jun 27, 2026
·
1 revision
How to contribute to HES.
We welcome contributions to HES! This guide will help you get started.
Use the "Bug Report" issue template on GitHub.
Use the "Feature Request" issue template on GitHub.
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request
- Fork the repository
- Make your changes
- Submit a pull request
- Git
- Python 3.12+
- Bash
git clone https://github.com/josemalyson/hes.git
cd hes# No dependencies required for core HES
# Optional: install development tools
pip install bandit semgrephes/
├── SKILL.md # Main orchestrator
├── skills/ # Skill files
│ ├── 00-bootstrap.md
│ ├── 01-discovery.md
│ └── ...
├── scripts/ # Helper scripts
│ ├── ci/
│ └── hooks/
├── .hes/ # Runtime state
│ ├── agents/
│ ├── state/
│ └── schemas/
└── .github/ # GitHub configuration
├── ISSUE_TEMPLATE/
└── workflows/
We use Conventional Commits:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
| Type | Description |
|---|---|
feat |
New feature or enhancement |
fix |
Bug fix |
docs |
Documentation changes |
chore |
Maintenance tasks |
refactor |
Code refactoring |
test |
Adding or modifying tests |
plan |
Architectural plan, roadmap |
stub |
Partial implementation |
feat(harness): add session manager skill
fix(bootstrap): handle missing state file gracefully
docs: add contribution guide
chore: update agent registry
plan(v4.0): add multi-agent orchestration roadmap
stub(planner): add task decomposition protocol
-
main— Protected branch, only merged via PRs -
feat/<n>— Feature branches -
fix/<n>— Bug fix branches -
docs/<n>— Documentation branches -
plan/<n>— Roadmap and architectural plans -
stub/<n>— Partial implementation of new agents
Every PR must include:
- Linked issue (bug or improvement)
- Description of changes
- Testing notes
- Updated documentation if behavior changed
- For stubs v4.0:
status: stubandtarget_versionin skill file header
## What
Brief description of the changes.
## Why
Why the changes are needed.
## Testing
What was tested and how.
## Related Issues
Closes #(issue number)# skill-name.md — Description
# version: X.Y.Z
# status: stable | stub
# target_version: X.Y.Z (if stub)
# HES Phase: PHASE_NAME | SYSTEMStubs are welcome when:
- The complete protocol is specified
- The header includes
status: stubandtarget_version - The footer includes
<!-- HES vX.Y STUB — implementation complete in vX.Y -->
- Create the skill file in
skills/ - Add the header with
status: stubandtarget_version - Update
.hes/agents/registry.json - Add the corresponding rule to
SKILL.md - Submit a PR
HES v4.0 is implementing 5 new agents. See Agents for details.
| Agent | Target | Status |
|---|---|---|
| planner.md | v3.6 | Stub ready |
| orchestrator.md | v3.7 | Stub ready |
| harness-evolver.md | v3.8 | Stub ready |
| optimizer.md | v3.9 | Stub ready |
| reviewer.md | v4.0 | Stub ready |
- Use clear headings
- Include code blocks with language tags
- Use tables for structured data
- Use
set -euo pipefail - Add comments for complex logic
- Use meaningful variable names
- Follow PEP 8
- Add type hints
- Write docstrings
- Install HES in a test project
- Run through the full workflow
- Verify all gates work correctly
# Run harness self-tests
/hes test
# Run CI validation
python scripts/ci/validate-harness.py- Open a Discussion
- Check the Wiki
- Read the README
Thank you for contributing!