Fix contradictary skill instruction
What the developer wrote
Authored by Nicolas Dorier
Fix contradictary skill instruction
What changed, and why it matters
This commit removes two contradictory sentences from an internal documentation file that tells contributors how to write pull request descriptions. One sentence had told them not to write about testing strategy, while another told them to add a testing note. The change only affects contributor guidance, not the BTCPay Server software that users or merchants interact with.
No security action needed. Treat as a normal documentation/process cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff edits .agents/skills/btcpayserver-pr-descriptions/SKILL.md, deleting the lines ‘Do not write about your testing strategy.’ and ‘Add a concise testing note that describes the user flow or scenario checked, not just the command that was run.’ No application code, configuration, dependency, or security control is modified.
Changed components
.agents/skills/btcpayserver-pr-descriptions/SKILL.mdInspect captured patch +0 / −2
### .agents/skills/btcpayserver-pr-descriptions/SKILL.md
@@ -12,7 +12,6 @@ Write pull request descriptions for the people who need to understand the change
- Assume most readers are non-technical users, merchants, admins, support people, translators, or reviewers trying to understand the product impact.
- Use technical details only when the pull request is itself technical and the details are necessary to review or explain the change.
- Avoid implementation jargon such as controller, view model, migration, refactor, endpoint, dependency injection, database schema, or renamed class unless that is the actual user-facing concern.
-- Do not write about your testing strategy.
## Content
@@ -34,7 +33,6 @@ Write pull request descriptions for the people who need to understand the change
- Start with a short paragraph explaining the functional change in plain language.
- Add screenshots or a short video when applicable.
-- Add a concise testing note that describes the user flow or scenario checked, not just the command that was run.
- Add technical notes only when they are necessary for reviewers, operators, integrators, or plugin authors.
## StyleWhy this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.