Skip to content

docs: document sync-tool-docs.yml workflow in AGENTS.md - #898

Merged
sergeykad merged 4 commits into
masterfrom
docs/add-sync-tool-docs-workflow
Apr 6, 2026
Merged

docs: document sync-tool-docs.yml workflow in AGENTS.md#898
sergeykad merged 4 commits into
masterfrom
docs/add-sync-tool-docs-workflow

Conversation

@sergeykad

Copy link
Copy Markdown
Collaborator

What does this PR do?

Documents the sync-tool-docs.yml workflow in AGENTS.md:

  1. Adds it to the CI/CD workflows table
  2. Updates the Tool Tags section to clarify that tools.json, README.md, and DOCS.md are auto-regenerated on merge — no manual python scripts/extract_tools.py needed

Discovered during review of #871 where a contributor correctly pointed out that stale doc references are cleaned up automatically by this workflow.

Type of change

  • Bug fix
  • New feature
  • Documentation
  • Maintenance/refactor
  • Breaking change

Testing

  • I have tested these changes with a LLM agent
  • All automated tests pass (uv run pytest)
  • Code follows style guidelines (uv run ruff check)

Checklist

  • I have updated documentation if needed

Add the workflow to the CI/CD table and update the Tool Tags section
to clarify that tools.json, README, and DOCS.md are auto-regenerated
on merge — no manual regeneration needed.
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request improves the project documentation by clarifying the automated nature of tool documentation and data synchronization. It ensures contributors are aware that manual script execution is no longer required for these tasks, as they are handled by the CI/CD pipeline.

Highlights

  • CI/CD Documentation: Added the sync-tool-docs.yml workflow to the CI/CD documentation table in AGENTS.md.
  • Tool Tag Clarification: Updated the Tool Tags section to clarify that documentation and tool data are automatically regenerated on merge, removing the need for manual script execution.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@sergeykad
sergeykad marked this pull request as ready for review April 6, 2026 14:31
@sergeykad
sergeykad requested a review from a team April 6, 2026 14:31
@sergeykad
sergeykad enabled auto-merge (squash) April 6, 2026 14:32

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

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.

Code Review

This pull request updates the AGENTS.md documentation to include the sync-tool-docs.yml workflow, which automates the regeneration of tools.json, README, and DOCS.md upon pushes to the master branch. The review feedback identifies two areas for improvement: correcting the documented trigger path for the workflow to src/ha_mcp/tools/ and ensuring that homeassistant-addon/DOCS.md is consistently listed as an auto-generated file in the Tool Tags section.

Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
- Fix trigger path: tools/ → src/ha_mcp/tools/
- Add homeassistant-addon/DOCS.md to Tool Tags section

@kingpanther13 kingpanther13 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Review

Good idea documenting this workflow — it was created in #849 (based on the extract_tools.py script from #839) and clearly not visible enough given the confusion on #871. Two accuracy issues to fix:

1. Trigger path is inaccurate

The table entry says Push to master (tools/) but the actual workflow triggers on src/ha_mcp/tools/** and scripts/extract_tools.py. The shorthand tools/ is misleading since there's no top-level tools/ directory. Should match the real paths:

| `sync-tool-docs.yml` | Push to master (`src/ha_mcp/tools/`, `scripts/extract_tools.py`) | Regenerate `tools.json`, README, DOCS.md |

2. Tool Tags section omits homeassistant-addon/DOCS.md

The workflow regenerates three files: site/src/data/tools.json, README.md, and homeassistant-addon/DOCS.md (visible in the workflow's git add step). The updated Tool Tags text mentions only the README table and tools.json. Should list all three so agents know the full scope of auto-generated files — this was the exact confusion that triggered this PR on #871.

@sergeykad

Copy link
Copy Markdown
Collaborator Author

Both issues from your review are addressed in the latest commits:

  1. Trigger path now includes both src/ha_mcp/tools/ and scripts/extract_tools.py
  2. homeassistant-addon/DOCS.md added to the Tool Tags section

@kingpanther13 kingpanther13 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Both issues from the previous review are addressed. Trigger paths and auto-generated file list now match the actual workflow. LGTM.

@sergeykad
sergeykad merged commit f793390 into master Apr 6, 2026
14 checks passed
@sergeykad
sergeykad deleted the docs/add-sync-tool-docs-workflow branch April 6, 2026 14:57
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