docs(skill): add no-editorializing rule for written output#98
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
documentation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request streamlines the 'When to Use' and 'Auto-merge Setup' sections in SKILL.md and introduces a new reference document, no-editorializing.md, which details guidelines for maintaining an objective tone in written artifacts. Feedback suggests updating the main heading of the new reference document to a level 1 heading (#) for proper Markdown structure and accessibility.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
Adds explicit guidance to the GitHub Project Skill documentation to avoid “editorializing” (writing about how good/careful work is rather than what it does), and links that guidance as a first-class reference within the skill docs. This fits the repo’s role as a set of reusable, opinionated (but actionable) GitHub configuration/workflow references.
Changes:
- Tightens/shortens the “When to Use” and “Auto-merge Setup” bullets in
SKILL.mdto keep the document concise. - Adds a new “No editorializing” section to
SKILL.mdand links to a dedicated reference page. - Introduces
references/no-editorializing.mdwith concrete tone-based tests and examples.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| skills/github-project/SKILL.md | Refines the skill’s quick guidance and adds an explicit “No editorializing” section + reference link. |
| skills/github-project/references/no-editorializing.md | New reference document defining and operationalizing the “no editorializing” writing rule. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
State what a change does, not how good or careful the work is; no narrating expected results or self-praise. Full rule in references/no-editorializing.md; SKILL.md kept under the 500-word limit by tightening a few triggers/prose. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
CybotTM
force-pushed
the
feat/no-editorializing-rule
branch
from
5a16d0a to
a216a4a
Compare
Address review: standalone reference doc starts with H1 (contra- -> counter- reaction); keep the 'Fork PR merge base' trigger consistent with the reference table. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Patch release. - No-editorializing rule for PR/issue/comment text: a `## No editorializing` note plus `references/no-editorializing.md`. (#98) Tag v2.15.5 after merge to publish.
Adds a
## No editorializingnote andreferences/no-editorializing.md: write what a change does, not how good or careful the work is — no narrating expected results or self-praise. Judged by tone (deletion / subject / voice tests), not a wordlist. SKILL.md kept under the 500-word limit by tightening a few triggers/prose. Mirrors netresearch/git-workflow-skill#83.