Link .agents skills into .claude/skills

[bholmesdev]

Description

• Symlinks code-comments, implementation, review-cycle, taste-review, test-desktop-app, write-product-spec, write-tech-spec from .agents/skills into .claude/skills. Unlinked, Claude Code's Skill tool can't see them.
• AGENTS.md: note that skills are written in .agents/skills and symlinked into .claude/skills.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation update

Testing

• Existing tests pass
• Added new tests for changes
• Tested manually (describe below)

Manual Testing Details:
Linked skills appear in Claude Code's Skill tool list.

Checklist

• I discussed this change in a GitHub issue before submitting this PR
• I have run the linter, formatter, and tests to ensure my code is ready for review

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
hubble-md-web	Ready	Preview	Sep 28, 2026 1:18pm UTC

[github-actions]

Overview

Links seven existing .agents/skills (code-comments, implementation, review-cycle, taste-review, test-desktop-app, write-product-spec, write-tech-spec) into .claude/skills with the same relative symlink pattern already used there, and documents that convention in AGENTS.md.

Concerns

None. Targets exist with SKILL.md; paths match working links (../../.agents/skills/<name>); no code/test changes.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

---

Reviewed by a Warp Factory agent.

[bholmesdev]

Merge risk: low

Impact: small ✅

• Contributor and agent tooling only; no app code.
• Symlinks become plain-text files on Windows checkouts without core.symlinks. That's already true of the existing .claude/skills links.

Rollback cost: low ✅

Error detection: N/A

Verification: good ✅

• Checked manually in Claude Code. All 18 .agents/skills entries now have a matching link.

Alignment: good ✅