Skip to content

nextchanges: Instruct agents to use a certain style for changelog entries - #6455

Merged
janniklasrose merged 2 commits into
mainfrom
janniklasrose/nextchanges-agent-instructions
Sep 2, 2026
Merged

nextchanges: Instruct agents to use a certain style for changelog entries#6455
janniklasrose merged 2 commits into
mainfrom
janniklasrose/nextchanges-agent-instructions

Conversation

@janniklasrose

@janniklasrose janniklasrose commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@janniklasrose
janniklasrose marked this pull request as ready for review September 2, 2026 15:07
Comment thread .agents/skills/pr-checklist/SKILL.md Outdated
- Create `.nextchanges/<section>/<name>.md`, picking the section folder that fits: `cli`, `bundles`, `dependency-updates`, `notable-changes`, or `api-changes`. `<name>` is arbitrary (a feature name or your PR number) — just keep it unique.
- Write a single line in user-facing language, no Jira links: start it with a `* ` bullet marker and end it with a period. Match the voice and tense of existing changelog entries.
- Write a single line in user-facing language, no Jira links: start it with a `* ` bullet marker and end it with a period.
- **Voice and tense: imperative mood, active voice, third person.** Lead with a verb that names the change — `Add`, `Fix`, `Bump`, `Remove`, `Deprecate`, `Support`, `Reject`, `Warn` — and describe the user-facing effect, not the implementation. Never use past tense (`Added`/`Fixed`) or first person (`we`/`I`/`our`). When a change reads better as a resulting behavior than as a verb, lead with the affected command, flag, or field in the present tense with "now".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

third person

That's not correct, right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, should be scrapped - avoiding first person doesn't mean using third person (which makes no sense for these types of sentences)

janniklasrose added a commit that referenced this pull request Sep 2, 2026
Addresses review feedback on #6455: avoiding first person doesn't imply
third person, which doesn't fit these entries. Keep imperative mood and
active voice.

Co-authored-by: Isaac <no-reply@databricks.com>
@janniklasrose
janniklasrose changed the base branch from janniklasrose/nextchanges-autofix to main September 2, 2026 18:07
janniklasrose and others added 2 commits September 2, 2026 20:14
Addresses review feedback on #6455: avoiding first person doesn't imply
third person, which doesn't fit these entries. Keep imperative mood and
active voice.

Co-authored-by: Isaac <no-reply@databricks.com>
@janniklasrose
janniklasrose force-pushed the janniklasrose/nextchanges-agent-instructions branch from 59894c2 to 7aa55c2 Compare September 2, 2026 18:16
@janniklasrose
janniklasrose added this pull request to the merge queue Sep 2, 2026
Merged via the queue into main with commit c995bc7 Sep 2, 2026
35 checks passed
@janniklasrose
janniklasrose deleted the janniklasrose/nextchanges-agent-instructions branch September 2, 2026 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants