source-unifier

Merge documentation from websites, GitHub, and PDFs while detecting conflicts.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/ai-writing-guide --skill source-unifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-unifier
Source: https://github.com/jmagly/ai-writing-guide/tree/main/.factory/skills/source-unifier
Command: npx skills add https://github.com/jmagly/ai-writing-guide --skill source-unifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges docs from websites, GitHub, and PDFs while detecting conflicts between docs and code.

Core Features & Use Cases

  • Conflict detection: Missing in code/docs, signature mismatches.
  • Unified configuration: Rule-based or AI-enhanced merging.
  • Conflict reporting: Annotated reports with remediation.

Quick Start

Unify docs from docs-site, GitHub repo, and a PDF manual with conflict report.

Frequently Asked Questions about source-unifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge documentation from multiple sources like GitHub repos and PDFs?

Merge documentation from multiple sources by ingesting docs from websites, GitHub repositories, and PDFs into a unified structure. source-unifier combines these sources while detecting conflicts between documentation and code, then outputs a consolidated documentation set with conflict annotations and provenance metadata showing where each piece came from.

Can I detect conflicts when merging documentation and code?

Conflict detection identifies mismatches such as missing implementations in code, signature differences between docs and actual code, and outdated documentation. The Skill flags these discrepancies in annotated reports so you can see exactly what conflicts exist and where remediation is needed.

What's the best way to handle conflicting information across documentation sources?

source-unifier supports both rule-based and AI-enhanced merge modes to resolve conflicts. Rule-based strategies apply predefined conflict-resolution logic, while AI-enhanced modes use reasoning to synthesize conflicting information, letting you choose the approach that fits your documentation workflow.

Do I need to manually configure how sources are merged?

Unified configuration allows you to define merge rules upfront or enable AI-enhanced merging for automatic synthesis. The Skill applies your chosen strategy across all sources, with verification steps built in to ensure the merged output meets your quality standards before generation.

How does source-unifier track where merged documentation came from?

The Skill generates output with unified references and provenance metadata, annotating each section with its source origin—whether from docs-site, GitHub, or PDF. This transparency lets readers trace information back to its original location and assess reliability.

What happens when documentation signatures don't match code implementations?

Signature mismatches and missing code implementations are flagged as conflicts during the merge process. The conflict report annotates these discrepancies with remediation guidance, helping you decide whether to update docs, code, or both.