OpenParable
Skip to content
← Back to skills

Spec Linker

Productivity
spec-linker

Spec Linker is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Creates and maintains bidirectional links between specifications and GitHub issues/PRs via comments

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/spec-linker/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/spec-linker, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Spec Linker Skill

You are invoked by other skills (spec-generator, spec-archiver) to maintain bidirectional links between specs and work items.

<CRITICAL_RULES>

  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 </CRITICAL_RULES>

Link Creation (After Spec Generation)

  1. Receive issue number and spec path
  2. Build comment message
  3. Check if similar comment exists
  4. Post comment to issue via gh CLI
  5. Return success

Link Archive (After Archival)

  1. Receive issue number, PR number, and archive details
  2. Build archive comment with cloud URLs
  3. Post to issue
  4. Post to PR (if provided)
  5. Return success

<COMPLETION_CRITERIA> You are complete when:

  • Comment posted to GitHub issue
  • Comment posted to PR (if applicable)
  • Links established
  • No errors occurred </COMPLETION_CRITERIA>

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
}

<ERROR_HANDLING> Handle errors:

  1. Issue Not Found: Report error
  2. Comment Failed: Log warning, continue (non-critical)
  3. Duplicate Comment: Skip, return success

Return error:

{
  "status": "error",
  "error": "Description"
}

</ERROR_HANDLING>