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:
Identify the GitHub issue number (e.g., 452) and title.
Execute the script from the root of the workspace to bootstrap the template:
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:
Issue File Created: The file issue-[num].md exists in the workspace root.
Reproduction Documented: The Bug Repro section contains the reproduction command and failure logs.
Upstream Compliance Checked: Commit sign-offs and linting checks are logged in Verify.
Workspace Cleaned: All temporary reproduction stubs, scripts, and logs outside of source modifications are removed.
1---2name: contribute-triage3description: Guides the agent to resolve an upstream issue using a local issue-[num].md file tracking reproduction, fix, and verification states.4license: MIT5---67# Open Source Contributor Triage89## Overview1011Contributing 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.1213---1415## Automated Execution Workflow1617When triaging a new issue, the AI agent must:18191. Identify the GitHub issue number (e.g., `452`) and title.202. Execute the script from the root of the workspace to bootstrap the template:2122```bash23./contribute-triage/contribute-triage.sh "ISSUE_NUM" "ISSUE_TITLE"24```25261. 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.2728---2930## State Sections in `issue-[num].md`3132The generated file contains three core sections. The agent must populate them with the following detailed items:3334* **Bug Repro**35 * **Failure Analysis:** A description of the observed bug or incorrect behavior.36 * **Reproduction Steps:** A checklist of manual or automated steps, including the exact command executed to trigger the failure.37 * **Failure Output:** A code block containing the raw compiler error, stack trace, or failure logs.38* **Fix**39 * **Goal:** A concise summary of the resolution target.40 * **Approach:** A description of the code modifications and files to be changed.41 * **Detailed Execution Checklist:** A step-by-step checklist tracking the implementation tasks.42* **Verify**43 * **Test Command:** The commands executed to verify the fix.44 * **Test Output Summary:** Logs or statistics confirming the tests passed.45 * **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.46 * **Cleanup Checklist:** Checkboxes confirming removal of temporary reproduction scripts, configuration files, and debug statement prints from the source.4748---4950## Verification Checklist5152Prior to completing the triage workflow, verify that:53541. [ ] **Issue File Created:** The file `issue-[num].md` exists in the workspace root.552. [ ] **Reproduction Documented:** The `Bug Repro` section contains the reproduction command and failure logs.563. [ ] **Upstream Compliance Checked:** Commit sign-offs and linting checks are logged in `Verify`.574. [ ] **Workspace Cleaned:** All temporary reproduction stubs, scripts, and logs outside of source modifications are removed.
Run npx skillmds@latest add victoriacheng15/contribute-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Guides the agent to resolve an upstream issue using a local issue-[num].md file tracking reproduction, fix, and verification states. It is listed under AI & ML on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.
victoriacheng15 (@victoriacheng15) published this skill. Their other Agent Skills are listed on their SkillMD profile.