Skip to content

fix: Update README with current project names and links#58

Merged
LucasSantana-Dev merged 1 commit intomainfrom
fix/readme-cleanup
Feb 28, 2026
Merged

fix: Update README with current project names and links#58
LucasSantana-Dev merged 1 commit intomainfrom
fix/readme-cleanup

Conversation

@LucasSantana-Dev
Copy link
Member

@LucasSantana-Dev LucasSantana-Dev commented Feb 28, 2026

Summary

  • Removed hardcoded "Version 1.2.0" (actual is v1.3.1, should use badges)
  • Fixed project names from old naming (forge-space-ui, forge-space-mcp) to current (siza, siza-mcp)
  • Fixed broken relative links (../uiforge-webapp/, ../../ECOSYSTEM_OVERVIEW.md) to GitHub URLs
  • Fixed npm package name from @uiforge/forge-patterns to @forgespace/core
  • Fixed directory name from uiforge-patterns/ to forge-patterns/
  • Added siza-gen and branding-mcp to projects list

Test plan

  • README renders correctly on GitHub
  • All links resolve to real pages
  • No references to old uiforge-* naming

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation

  • Updated installation instructions with new package identifiers to reflect current project structure
  • Reorganized project references and links with updated naming conventions
  • Enhanced repository structure documentation with current directory naming
  • Streamlined project listings and related references for improved navigation and accessibility

- Remove hardcoded version 1.2.0 (use badges instead)
- Fix project names: forge-space-ui → siza, forge-space-mcp → siza-mcp
- Fix broken relative links to use GitHub URLs
- Fix npm package name: @uiforge/forge-patterns → @forgespace/core
- Fix directory name in structure: uiforge-patterns → forge-patterns
- Add siza-gen and branding-mcp to projects list
@coderabbitai
Copy link

coderabbitai bot commented Feb 28, 2026

📝 Walkthrough

Walkthrough

This PR updates the README.md file with project rebranding and reorganization, including renaming projects (uiforge-patterns to Forge Space/Siza components), updating installation commands, adjusting project listings, and refreshing documentation references. No code or API changes are introduced.

Changes

Cohort / File(s) Summary
Documentation Update
README.md
Updated project names and links (mcp-gateway → siza, uiforge → siza/forgespace), changed npm install target from @uiforge/forge-patterns to @forgespace/core, revised repository structure directory names, and reorganized related projects section with new documentation references.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Poem

🐰 Whiskers twitched with glee—the README now sings,
Of Siza reborn and the new names we bring,
Old forge patterns rest, new pathways unfold,
A cleaner, brighter story, more daring and bold!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating README with current project names and links, which directly aligns with the primary objectives of renaming legacy projects and fixing broken references.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/readme-cleanup

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
README.md (1)

186-189: ⚠️ Potential issue | 🟡 Minor

Update feature toggle examples to use new project names.

Lines 187-189 still reference the old project names forge-space-ui and forge-space-mcp. These should be updated to siza and siza-mcp respectively to align with the current project rebranding used elsewhere in the README.

Proposed fix
 forge-features enable mcp-gateway.rate-limiting
-forge-features enable forge-space-ui.rate-limiting
-forge-features enable forge-space-mcp.ai-chat
-forge-features enable forge-space-ui.dark-mode
+forge-features enable siza.rate-limiting
+forge-features enable siza-mcp.ai-chat
+forge-features enable siza.dark-mode
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 186 - 189, Update the feature toggle examples by
replacing the old project names in the CLI lines: change "forge-space-ui" to
"siza" and "forge-space-mcp" to "siza-mcp" in the existing "forge-features
enable" commands so the examples read "forge-features enable siza.rate-limiting"
and "forge-features enable siza-mcp.ai-chat" (and similarly for the dark-mode
toggle).
🧹 Nitpick comments (1)
README.md (1)

49-50: Consider using absolute GitHub URLs for consistency.

The PR objectives mention replacing broken relative links with absolute GitHub URLs. While these relative links should work correctly (they point to files within the same repository), using absolute URLs would be more consistent with the stated approach and would make the links work in any context (e.g., when the README is viewed outside GitHub).

🔗 Proposed change to use absolute URLs
-- [**Documentation Hub**](docs/README.md) - Complete documentation
-- [**Project Context**](docs/project/PROJECT_CONTEXT.MD) - Project guide and context
+- [**Documentation Hub**](https://github.com/Forge-Space/core/blob/main/docs/README.md) - Complete documentation
+- [**Project Context**](https://github.com/Forge-Space/core/blob/main/docs/project/PROJECT_CONTEXT.MD) - Project guide and context
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 49 - 50, Replace the two relative links in README.md
(the link texts "Documentation Hub" and "Project Context") with absolute GitHub
URLs pointing to the corresponding files in this repository (e.g.,
https://github.com/<owner>/<repo>/blob/main/docs/README.md and
https://github.com/<owner>/<repo>/blob/main/docs/project/PROJECT_CONTEXT.MD),
updating the markdown so the links work consistently outside the repo and follow
the PR's objective of using absolute URLs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 46: The "Siza MCP" README link text ([**Siza MCP**]) currently points to
the wrong repository (ui-mcp); update the markdown link target to the correct
repo name (siza-mcp) so the link becomes the siza-mcp URL, mirroring the fix
applied at the earlier occurrence; locate the "[**Siza MCP**]" entry and replace
its href to use "siza-mcp" instead of "ui-mcp".

---

Outside diff comments:
In `@README.md`:
- Around line 186-189: Update the feature toggle examples by replacing the old
project names in the CLI lines: change "forge-space-ui" to "siza" and
"forge-space-mcp" to "siza-mcp" in the existing "forge-features enable" commands
so the examples read "forge-features enable siza.rate-limiting" and
"forge-features enable siza-mcp.ai-chat" (and similarly for the dark-mode
toggle).

---

Nitpick comments:
In `@README.md`:
- Around line 49-50: Replace the two relative links in README.md (the link texts
"Documentation Hub" and "Project Context") with absolute GitHub URLs pointing to
the corresponding files in this repository (e.g.,
https://github.com/<owner>/<repo>/blob/main/docs/README.md and
https://github.com/<owner>/<repo>/blob/main/docs/project/PROJECT_CONTEXT.MD),
updating the markdown so the links work consistently outside the repo and follow
the PR's objective of using absolute URLs.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e878801 and 5efb212.

📒 Files selected for processing (1)
  • README.md

- [**Forge Space - UI MCP**](../uiforge-mcp/) - Specialized UI development tools
- [**Siza**](https://github.com/Forge-Space/siza) - AI-powered full-stack workspace
- [**MCP Gateway**](https://github.com/Forge-Space/mcp-gateway) - Central tool aggregation and routing
- [**Siza MCP**](https://github.com/Forge-Space/ui-mcp) - MCP server for UI generation
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

Critical: Same URL mismatch for Siza MCP.

The same issue as Line 29 - "Siza MCP" links to ui-mcp instead of siza-mcp.

🔗 Proposed fix for the URL
-- [**Siza MCP**](https://github.com/Forge-Space/ui-mcp) - MCP server for UI generation
+- [**Siza MCP**](https://github.com/Forge-Space/siza-mcp) - MCP server for UI generation
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- [**Siza MCP**](https://github.com/Forge-Space/ui-mcp) - MCP server for UI generation
- [**Siza MCP**](https://github.com/Forge-Space/siza-mcp) - MCP server for UI generation
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 46, The "Siza MCP" README link text ([**Siza MCP**])
currently points to the wrong repository (ui-mcp); update the markdown link
target to the correct repo name (siza-mcp) so the link becomes the siza-mcp URL,
mirroring the fix applied at the earlier occurrence; locate the "[**Siza MCP**]"
entry and replace its href to use "siza-mcp" instead of "ui-mcp".

@LucasSantana-Dev LucasSantana-Dev merged commit fc09f63 into main Feb 28, 2026
15 checks passed
@LucasSantana-Dev LucasSantana-Dev deleted the fix/readme-cleanup branch February 28, 2026 19:40
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.

1 participant