feat: add project-level skill support in skill_domains

[cuioss-oliver]

Summary

• Add project:{skill} notation for project-level skills in skill_domains, allowing .claude/skills/ skills to be discovered and attached to any configured domain
• New verbs: skill-domains discover-project and skill-domains attach-project for discovery and attachment
• skill-domains configure now preserves project_skills across reconfiguration
• get_skill_description() resolves project: prefix from .claude/skills/ directory
• Rename executor internal local: prefix to default-bundle: to avoid confusion with user-facing project: notation
• Fix TOON serializer round-trip fidelity: quote string values that would be misinterpreted as numbers/booleans/null (fixes flaky CI tests)

Test plan

• 322-line test suite for all new skill-domains functionality (discover, attach, configure preservation, get resolution)
• TOON serializer fix verified — 1696/1696 tests pass
• ./pw verify plan-marshall passes (744 tests)
• ./pw verify pm-workflow passes (341 tests)
• Full ./pw module-tests passes (1696 tests)

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @cuioss-oliver, 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 introduces project-level skill support, enhancing the flexibility and discoverability of skills within specific projects. It also addresses a critical bug in the TOON serializer, ensuring data integrity and test stability. The changes include new commands for skill management, preservation of existing configurations, and internal refactoring for clarity.

Highlights

• Project-Level Skills: Introduced support for project-level skills, enabling discovery and attachment of skills from the .claude/skills/ directory to configured domains.
• New Commands: Added skill-domains discover-project and skill-domains attach-project commands for discovering and attaching project-level skills.
• Configuration Preservation: Ensured that skill-domains configure preserves project_skills across reconfiguration.
• TOON Serializer Fix: Fixed the TOON serializer to correctly quote string values that could be misinterpreted as numbers, booleans, or null, resolving flaky CI tests.
• Internal Prefix Rename: Renamed the executor internal local: prefix to default-bundle: to avoid confusion with the user-facing project: notation.

Activity

• Added project-level skill support in skill_domains
• Introduced project:{skill} notation for project-level skills in skill_domains
• Added skill-domains discover-project and skill-domains attach-project verbs
• Ensured skill-domains configure preserves project_skills across reconfiguration
• Implemented get_skill_description() to resolve project: prefix from .claude/skills/ directory
• Renamed executor internal local: prefix to default-bundle:
• Fixed TOON serializer round-trip fidelity

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

This pull request introduces project-level skill support, which is a significant feature enhancement. The changes are well-structured, with new commands for discovering and attaching project skills, and updates to preserve this configuration. The renaming of the internal local: prefix to default-bundle: improves clarity. The fix for the TOON serializer also increases the robustness of the system. The accompanying test suite is comprehensive and covers the new functionality thoroughly.

I have one comment regarding code duplication in a fallback function within a core module, which seems to be caused by an incorrect import path. Addressing this would improve the maintainability of the code and align with the principle of maintaining a minimal internal dependency footprint.