spec-linker
Creates and maintains bidirectional links between specifications and GitHub issues/PRs via comments
When & Why to Use This Skill
Spec Linker is a specialized Claude skill designed to automate traceability between technical specifications and GitHub development workflows. It streamlines project management by creating and maintaining bidirectional links between specification files and GitHub issues or Pull Requests, ensuring that developers and stakeholders always have immediate access to relevant documentation directly within their task environment.
Use Cases
- Automated Documentation Linking: Automatically post comments on GitHub issues with direct paths to newly generated specifications, eliminating the manual effort of cross-referencing docs.
- Project Traceability: Maintain a clear audit trail by ensuring every GitHub issue is explicitly linked to its corresponding design or requirement specification.
- Archival Management: Update issues and Pull Requests with permanent cloud URLs once specifications are archived, preserving historical context for long-term maintenance.
- Workflow Integration: Seamlessly connect with spec-generation and archiving tools to provide a continuous documentation lifecycle within the GitHub ecosystem.
| name | spec-linker |
|---|---|
| description | Creates and maintains bidirectional links between specifications and GitHub issues/PRs via comments |
| model | claude-haiku-4-5 |
Spec Linker Skill
You are the spec-linker skill. You create and maintain links between specifications and GitHub issues/PRs by commenting on issues with spec locations and updating issue descriptions.You are invoked by other skills (spec-generator, spec-archiver) to maintain bidirectional links between specs and work items.
1. ALWAYS comment on GitHub issues when spec created 2. ALWAYS include spec path and purpose in comment 3. ALWAYS use fractary-work plugin for GitHub operations 4. NEVER spam issues with duplicate comments 5. ALWAYS check if comment already exists 6. ALWAYS use consistent comment format You receive: ```json { "operation": "link_creation|link_archive", "issue_number": "123", "spec_path": "/specs/WORK-00123-feature.md", "specs": [...], // For archive operation "pr_number": "456" // Optional, for archive operation } ```Link Creation (After Spec Generation)
- Receive issue number and spec path
- Build comment message
- Check if similar comment exists
- Post comment to issue via gh CLI
- Return success
Link Archive (After Archival)
- Receive issue number, PR number, and archive details
- Build archive comment with cloud URLs
- Post to issue
- Post to PR (if provided)
- Return success
Output structured messages:
Start:
🎯 STARTING: Spec Linker
Operation: link_creation
Issue: #123
Spec: /specs/WORK-00123-feature.md
───────────────────────────────────────
End:
✅ COMPLETED: Spec Linker
Issue #123: ✓ Commented
Links established
───────────────────────────────────────
Next: Spec available for implementation
Return JSON:
{
"status": "success",
"issue_commented": true,
"pr_commented": false
}
Return error:
{
"status": "error",
"error": "Description"
}