Add Goose skills support (.goose/skills/)

[github-actions]

Implementation complete. I've added Goose skills support with the following changes:

1. src/features/skills/goose-skill.ts - New GooseSkill class that:

   • Generates skills to .goose/skills/<name>/SKILL.md
   • Follows the Agent Skills specification with name and description frontmatter
   • Supports project scope only (no global mode)
   • Targeted by "goose" or "*" in rulesync skill targets

2. src/features/skills/skills-processor.ts - Registered goose target in:

   • skillsProcessorToolTargetTuple
   • toolSkillFactories map with supportsProject: true, supportsSimulated: false, supportsGlobal: false

3. src/features/skills/goose-skill.test.ts - 13 tests covering all methods

4. src/features/skills/skills-processor.test.ts - Updated expected targets to include goose

Closes #1115

github run

[dyoshikawa]

\oc レビューお願い

[dyoshikawa]

/oc レビューお願い

[dyoshikawa]

/oc #1149 (comment) このレビューコメントの指摘を修正してください。

[dyoshikawa]

/oc review

[dyoshikawa]

/oc review

[dyoshikawa]

/oc review

[dyoshikawa]

/oc review

[github-actions]

PR #1149 Review: Add Goose Skills Support

Code Review Summary

Overall Assessment: ⭐ 4/5 - Request Changes

✅ Strengths

• Excellent pattern adherence (mirrors ReplitSkill, KiroSkill, CursorSkill)
• Proper type safety with z.looseObject() schema
• Complete static method implementation
• Name matching validation (frontmatter name matches directory)
• Correct SkillsProcessor integration
• Good test coverage (13 tests)

🔴 Blocking Issue

Documentation Markdown Formatting Error (docs/reference/file-formats.md, skills/rulesync/file-formats.md)

The Goose skills section has malformed code fence closing - extra `````` on line 193 will render improperly.

🟡 Minor Issues

• Missing test for invalid frontmatter (missing description)
• Missing constructor test for name mismatch validation

---

Security Review Summary

Overall Risk Level: LOW ✅ - APPROVE

Area	Status
Path Traversal	✅ Protected via AiDir base class
Input Validation	✅ Zod schema + name-directory consistency check
Injection	✅ None found
Global Mode	✅ Correctly throws error

The implementation properly inherits security protections and follows established secure patterns.

---

Action Required Before Merge

1. Required: Fix code fence formatting in docs/reference/file-formats.md and skills/rulesync/file-formats.md (remove extra ``````)
2. Optional: Add edge case tests for invalid frontmatter

github run