# Contribute Triage

> Guides the agent to resolve an upstream issue using a local issue-[num].md file tracking reproduction, fix, and verification states.

- Skill: `victoriacheng15/contribute-triage` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add victoriacheng15/contribute-triage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/victoriacheng15/contribute-triage/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: victoriacheng15 (https://skillmd.com/u/victoriacheng15)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/victoriacheng15/contribute-triage

---


# Open Source Contributor Triage

## Overview

Contributing to open-source repositories requires systematic triage, local bug reproduction, code implementation, and compliance with upstream project standards. This skill automates the tracking of this process in a single, local, non-committed `issue-[num].md` file in the workspace root.

---

## Automated Execution Workflow

When triaging a new issue, the AI agent must:

1. Identify the GitHub issue number (e.g., `452`) and title.
2. Execute the script from the root of the workspace to bootstrap the template:

```bash
./contribute-triage/contribute-triage.sh "ISSUE_NUM" "ISSUE_TITLE"
```

1. Progressively edit the metadata header (Issue Link, PR Link, Target Branch, Subsystem) and complete the generated `issue-[num].md` file's three core sections as the lifecycle advances.

---

## State Sections in `issue-[num].md`

The generated file contains three core sections. The agent must populate them with the following detailed items:

* **Bug Repro**
  * **Failure Analysis:** A description of the observed bug or incorrect behavior.
  * **Reproduction Steps:** A checklist of manual or automated steps, including the exact command executed to trigger the failure.
  * **Failure Output:** A code block containing the raw compiler error, stack trace, or failure logs.
* **Fix**
  * **Goal:** A concise summary of the resolution target.
  * **Approach:** A description of the code modifications and files to be changed.
  * **Detailed Execution Checklist:** A step-by-step checklist tracking the implementation tasks.
* **Verify**
  * **Test Command:** The commands executed to verify the fix.
  * **Test Output Summary:** Logs or statistics confirming the tests passed.
  * **Upstream Compliance Checklist:** Checkboxes verifying DCO commit sign-offs (`git commit -s` if required by upstream), code style formatting, repository PR template completion, and adding/verifying that all unit/integration tests pass.
  * **Cleanup Checklist:** Checkboxes confirming removal of temporary reproduction scripts, configuration files, and debug statement prints from the source.

---

## Verification Checklist

Prior to completing the triage workflow, verify that:

1. [ ] **Issue File Created:** The file `issue-[num].md` exists in the workspace root.
2. [ ] **Reproduction Documented:** The `Bug Repro` section contains the reproduction command and failure logs.
3. [ ] **Upstream Compliance Checked:** Commit sign-offs and linting checks are logged in `Verify`.
4. [ ] **Workspace Cleaned:** All temporary reproduction stubs, scripts, and logs outside of source modifications are removed.