Skip to content

Update Claude plugin command and improve documentation consistency#118

Open
tobimeira wants to merge 4 commits into
firebase:mainfrom
tobimeira:claude/add-claude-documentation-YgQI8
Open

Update Claude plugin command and improve documentation consistency#118
tobimeira wants to merge 4 commits into
firebase:mainfrom
tobimeira:claude/add-claude-documentation-YgQI8

Conversation

@tobimeira
Copy link
Copy Markdown

Summary

This PR adds a CLAUDE.md file to the repository root, providing a comprehensive codebase guide for AI assistants (Claude Code, Cursor, GitHub Copilot, Gemini CLI, etc.).

Changes

  • Add CLAUDE.md: A structured guide covering project overview, repository structure, skill file format, key conventions, development workflows, branch strategy, CI/CD pipeline, and multi-platform configuration reference.
    • Fix naming inconsistency: Corrects a minor inconsistency in CLAUDE.md.
    • Remove hardcoded reviewers: Cleans up hardcoded reviewer references.

Motivation

Having a CLAUDE.md at the repo root helps AI coding assistants quickly understand the codebase structure, conventions, and workflows, improving the quality and consistency of AI-assisted contributions.

charlotteliang and others added 4 commits February 11, 2026 09:52
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Documents the repository structure, skill file format, key conventions
(npx-first Firebase CLI usage), development workflows, branch strategy,
CI/CD automation, and multi-platform configuration files.

https://claude.ai/code/session_01AmV45yVaRjj5FcHUmN3Lj1
- Use 'firebase-skills/' as the root dir name to match README.md
- Update symlink example path to use 'firebase-skills' consistently
- Replace hardcoded reviewer usernames with 'designated repository maintainers'

https://claude.ai/code/session_01AmV45yVaRjj5FcHUmN3Lj1
@google-cla
Copy link
Copy Markdown

google-cla Bot commented May 12, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces CLAUDE.md, a comprehensive codebase guide for the Firebase Agent Skills repository. The document outlines the project structure, skill file formats, development workflows, and CI/CD processes. Feedback was provided to address inconsistencies in the documentation regarding skill naming conventions and the MCP configuration example, ensuring they align with existing repository patterns.

Comment thread CLAUDE.md

```yaml
---
name: firebase-{feature-name} # kebab-case, matches directory name
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.

medium

The naming convention firebase-{feature-name} specified here is inconsistent with several skills listed in the "Repository Structure" section, such as xcode-project-setup and the developing-genkit-* skills. It would be more accurate to use a more general placeholder to reflect the actual directory naming policy.

Suggested change
name: firebase-{feature-name} # kebab-case, matches directory name
name: {skill-name} # kebab-case, matches directory name

Comment thread CLAUDE.md
Comment on lines +222 to +223
"args": ["-y", "firebase-tools@latest", "mcp", "--dir", "."],
"env": { "IS_FIREBASE_MCP": "true" }
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.

medium

This MCP configuration example is inconsistent with the existing gemini-extension.json file in the repository. The example includes --dir . and uses the environment variable IS_FIREBASE_MCP, whereas gemini-extension.json omits the directory flag and uses IS_GEMINI_CLI_EXTENSION. Since this is described as the entry point for "all platforms", these should be aligned or the differences should be clarified to ensure documentation consistency.

Suggested change
"args": ["-y", "firebase-tools@latest", "mcp", "--dir", "."],
"env": { "IS_FIREBASE_MCP": "true" }
"args": ["-y", "firebase-tools@latest", "mcp"],
"env": { "IS_GEMINI_CLI_EXTENSION": "true" }

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.

3 participants