[AlexProgrammerDE]

Update the example plugin display metadata, publication description, documentation, and contribution forms to Soulfire. Preserve plugin IDs, Java types and packages, artifact coordinates, and repository URLs.

Passed ./gradlew build test spotlessCheck. The project has no test sources. SpotBugs reports the existing mixin cast warning; the configured build succeeds.

Part of the coordinated Soulfire display-brand migration: soulfiremc-com/brand#2. The existing cyan flame remains the product mark. Related app PR: soulfiremc-com/SoulFireClient#1215. External profiles, repository descriptions, store listings, and live releases require separate service updates.

Created with gpt-6.1-sol in T3 Code through the Codex harness.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

Several “SoulFire” references change to “Soulfire.” The README title and the plugin display name also change. Some listed issue-template and support text ranges show no wording change.

Changes: Branding and project text

Layer / File(s)	Summary
Repository documentation and templates .github/ISSUE_TEMPLATE/*, .github/pull_request_template.md, AGENTS.md, CONTRIBUTING.md, README.md, SUPPORT.md	CONTRIBUTING.md changes several “SoulFire” references to “Soulfire.” The README title changes, and the API reference guidance appears in a separate paragraph. Other listed template and support text ranges show no wording change.
Project and plugin display text build.gradle.kts, src/main/java/com/soulfiremc/pluginexample/ExampleServerExtension.java	The project description and plugin display name change “SoulFire” to “Soulfire.”

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · up to 74e2d

The Soulfire naming updates present no identified merge-blocking risk. The change is ready to merge subject to normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title "feat(branding): use Soulfire in the plugin example" matches the main change. The changeset renames the product from SoulFire to Soulfire across the example plugin's display metadata, docs, …
Description check		The description covers the change, the validation, and the scope limits, so it is mostly complete against the template. The author states that the build, tests, and spotlessCheck passed, and that the …
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title "feat(branding): use Soulfire in the plugin example" matches the main change. The changeset renames the product from SoulFire to Soulfire across the example plugin's display metadata, docs, build description, and issue templates. The title is a Conventional Commit and is 50 characters long. It does not describe the preserved identifiers or the external service updates, which is expected for a title.

Full details: Description check

Explanation

The description covers the change, the validation, and the scope limits, so it is mostly complete against the template. The author states that the build, tests, and spotlessCheck passed, and that the project has no test sources. It names the preserved plugin IDs, Java types, packages, artifact coordinates, and repository URLs, which serves as the compatibility statement. It links the related brand and app PRs and notes that external profiles and store listings need separate updates. It does not use the template headings, does not include the Closes line or a Conventional Commit checklist, and does not name the SoulFire version used for plugin load checks. These gaps are minor.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 2 files. (7 skipped: 7 unsupported.)

Finishing Touches

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 2076387d-b908-4736-8f12-0da1518a7db2

Commits

Reviewing files that changed from the base of the PR and between 9ea38b6 and 74e2d4d.

Files selected for processing: 9

• .github/ISSUE_TEMPLATE/bug-report.yml
• .github/ISSUE_TEMPLATE/config.yml
• .github/pull_request_template.md
• AGENTS.md
• CONTRIBUTING.md
• README.md
• SUPPORT.md
• build.gradle.kts
• src/main/java/com/soulfiremc/pluginexample/ExampleServerExtension.java

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.