Github Issue To Pr — Carry a GitHub issue to a verified PR with honest CI state
Github Issue To Pr — Carry a GitHub issue to a verified PR with honest CI state
Start with meaning, then move to detail.
This lesson explains Github Issue To Pr — Carry a GitHub issue to a verified PR with honest CI state as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, open the source, choose one section, and write an expected result before changing configuration.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to Use, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Github Issue To Pr — Carry a GitHub issue to a verified PR with honest CI state without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Write one sentence describing what should change after applying this topic.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Carry a GitHub issue to a verified PR with honest CI state
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When to Use
Read this after the foundation, then connect it to the previous step.
- 04Procedure
Read this after the foundation, then connect it to the previous step.
- 051. Read the live issue — body AND full thread
Read this after the foundation, then connect it to the previous step.
- 062. Sweep for existing and duplicate work
Read this after the foundation, then connect it to the previous step.
- 073. Validate the premise against current code — and against design intent
Read this after the foundation, then connect it to the previous step.
- 084. Define acceptance and risk
Read this after the foundation, then connect it to the previous step.
- 095. Implement the smallest complete change — and fix the class
Read this after the foundation, then connect it to the previous step.
- 106. Prove the regression test bites (sabotage run)
Finish here to verify the result and special cases.
Write one sentence describing what should change after applying this topic.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.