# Contribute to PenguinHarness

Source: https://club.penguin.ooo/workflow/harness/

- Target Repository: [PenguinHarness](https://github.com/Prism-Shadow/penguin-harness)
- Community Issues: [for-community Issues](https://github.com/Prism-Shadow/penguin-harness/issues?q=state%3Aopen%20label%3A%22for-community%22)

## Contribution Workflow

1. **Claim or Open an Issue**: Browse open Issues labeled `for-community` in the PenguinHarness repository ([view `for-community` Issues](https://github.com/Prism-Shadow/penguin-harness/issues?q=state%3Aopen%20label%3A%22for-community%22)), or open a new Issue under this topic for a feature request or bug fix.
2. **Claim in Issue Comments (Optional)**: Leave a comment on the Issue to claim the task (claiming is optional and primarily prevents duplicate work).
3. **Submit a PR**: Implement the change, run tests and checks, and open a Pull Request in [PenguinHarness](https://github.com/Prism-Shadow/penguin-harness) linked to the Issue.
4. **Maintainer Review & Merge**: Wait for a maintainer to review the code and merge the PR after approval.

## Format Examples

### 1. Issue Example

**Title**: `[Feature / Fix] <Short description of the feature or bug fix>`

```markdown
### Background & Goal
- Describe the problem to solve or the feature to add in PenguinHarness

### Proposed Approach
- Outline the modules to update and the implementation plan
```

### 2. Issue Claim Comment Example (Optional)

```markdown
I would like to work on this Issue and plan to submit a PR by YYYY-MM-DD.
```

### 3. PR Example

**Title**: `feat: <short description>` (or `fix: <short description>`)

```markdown
Closes #<issue-number>

### Summary
- Summarize the feature or fix implemented in this PR

### Verification
- [x] Passed project unit tests, type checks, and build verification
```