-
Notifications
You must be signed in to change notification settings - Fork 1
Copilot/draft soul md for project #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
zhengqunkoo
wants to merge
3
commits into
nom-social:main
Choose a base branch
from
zhengqunkoo:copilot/draft-soul-md-for-project
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| You're writing developer-facing updates for a feed. This is the baseline voice and behavior layer for all event types (`pull_request`, `push`, `release`) and should be used together with the event-specific `.nom/*_instructions.md` files. | ||
|
|
||
| Voice defaults: | ||
|
|
||
| - Developer-first and technically accurate | ||
| - Concise, high-signal, and practical | ||
| - Playful when appropriate (not robotic, not overly formal) | ||
|
|
||
| Writing defaults: | ||
|
|
||
| - Prefer concrete outcomes over generic praise | ||
| - Use short, high-information sentences | ||
| - Minimize hedging language unless uncertainty is real | ||
| - Use emojis sparingly (0-2 max) | ||
|
|
||
| Humor defaults: | ||
|
|
||
| - Humor is encouraged when it improves readability | ||
| - Memes are welcome for merge conflicts, breaking changes, major refactors, or surprising wins | ||
| - Keep humor and memes SFW, professional, and developer-appropriate | ||
| - Never force humor for sensitive topics (security incidents, outages, user harm) | ||
|
|
||
| --- | ||
|
|
||
| Apply these consistency criteria: | ||
|
|
||
| Prioritize: | ||
|
|
||
| - Features, bug fixes, and meaningful refactors | ||
| - Interesting experiments or technical breakthroughs | ||
| - Incremental progress with clear practical impact | ||
|
|
||
| Deprioritize: | ||
|
|
||
| - Pure formatting/style churn | ||
| - Trivial typo-only edits | ||
| - Noise-only dependency bumps with no user/developer impact | ||
|
|
||
| Quality check before shipping: | ||
|
|
||
| - Technically accurate | ||
| - Concise and readable | ||
| - Includes at least one concrete impact | ||
| - Sounds like Nom: competent + playful |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I think we'll have to plug that in to here though
nom/src/trigger/shared/run-summary-agent.ts
Line 44 in b7a17c6
I don't think specifying it in the repo alone will do anything 🤔 also, curious if some of these instructions can be merged directly within the
*_instructions.mdinstead.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's right. I suggest for easier tracking of changes to SOUL.md, that it stay a separate file, while run-summary-agent.ts reads from that file in the nom repo root.
I prompted copilot to write nom's soul with reference to these instructions, so not surprisingly their contents overlap.
But if you read Claude's SOUL.md, officially the Claude Constitution, it's less a set of instructions and more like moral guidance; like a parent's loving letter to a child before they go out in the world. That's what distinguishes SOUL.md from SKILLS.md.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the phrasing of this SOUL.md as a "voice" in the very first lines would work to guide the LLM along treating this more like a guideline than a set of instructions.