chore: replace generic emails with GitHub references

[CybotTM]

Summary

• Replace generic @netresearch.de email addresses with GitHub-native references
• Add support section to package metadata with Issues/Source URLs
• Use GitHub Security Advisories for vulnerability reporting
• Use GitHub Issues for general support/contact

Motivation

Generic email addresses in public repositories attract spam and create maintenance overhead. GitHub provides better mechanisms for each use case:

• Security: Private vulnerability reporting via Security Advisories
• Support: Issue tracker with templates and labels
• Contact: Discussions for general questions

Test plan

• Verify package metadata is valid (composer validate)
• Verify links in documentation point to correct URLs
• Verify no functional email addresses were removed (only metadata/docs)

[gemini-code-assist]

Summary of Changes

Hello @CybotTM, I'm Gemini Code Assist¹! 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 modernizes the project's contact and support information by transitioning from generic email addresses to GitHub-native references. The changes update package metadata to direct users to GitHub for support issues and source code, aligning with best practices for public repositories to reduce spam and streamline communication channels.

Highlights

• Metadata Update: Replaced generic email addresses with GitHub repository URLs in the .claude-plugin/plugin.json and composer.json files.
• Support Information: Added dedicated support sections to plugin.json and composer.json to specify GitHub Issues and Source URLs, streamlining contact and support channels.

Changelog

• .claude-plugin/plugin.json
  • Replaced the author's email with a GitHub repository URL.
  • Added a support section with a link to GitHub Issues.
• composer.json
  • Removed the author's email address.
  • Added a support section including links to GitHub Issues and the source repository.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[gemini-code-assist]

Code Review

The changes successfully transition the project's metadata from generic email contacts to GitHub-native references. This improves security by using GitHub's private vulnerability reporting and reduces spam. I have provided suggestions to improve consistency between the manifest files and to enhance the discoverability of documentation.

[gemini-code-assist]

The author URL here points to the repository, while in composer.json it points to the company website. For consistency in how the author entity is referenced across manifests, consider using the same URL.

Suggested change

	"url": "https://github.com/netresearch/github-project-skill"
	"url": "https://www.netresearch.de/"

[gemini-code-assist]

To align with the support section in composer.json and the PR's stated goal of adding Source URLs, consider including the source link here as well.

    "issues": "https://github.com/netresearch/github-project-skill/issues",
    "source": "https://github.com/netresearch/github-project-skill"

[gemini-code-assist]

Including a docs link in the support section improves discoverability of the project's documentation (e.g., the SKILL.md file).

    "issues": "https://github.com/netresearch/github-project-skill/issues",
    "source": "https://github.com/netresearch/github-project-skill",
    "docs": "https://github.com/netresearch/github-project-skill"