Sigint Migrate Skill Skill

Sigint Migrate Skill

Migrates legacy sigint configuration to the v2.0 JSON format with per-topic support. Safe to run multiple times (idempotent). Always backs up source files before overwriting.

Structured Data Protocol: JSON file creation MUST follow protocols/STRUCTURED-DATA.md. Use jq via Bash for writing sigint.config.json. Every write MUST be followed by schema validation using schemas/sigint-config.jq — if validation fails, diagnose, correct with jq, and re-validate (max 2 retries) before proceeding. See the Retry-and-Correct protocol in protocols/STRUCTURED-DATA.md.

Arguments

Parse $ARGUMENTS:

--dry-run → dry_run = true — preview what would be written, no files modified
--global → migrate_global = true — also migrate ~/.claude/sigint.local.md (default: project only)

Phase 0: Detect Source Files

Step 0.1: Inventory legacy config files

Check for each (silent, no errors if missing):

project_local_md — ./.claude/sigint.local.md exists
global_local_md — ~/.claude/sigint.local.md exists (relevant only if migrate_global)
project_config_v1 — ./.sigint.config.json exists and its version field is "1.0" (if version is missing or not "1.0", ignore this file and emit: "Skipping .sigint.config.json — version is not 1.0.")
target_exists — ./sigint.config.json exists

Step 0.2: Check for existing v2.0 target

If ./sigint.config.json exists:

Parse it. If version == "2.0":

AskUserQuestion(
  question: "sigint.config.json v2.0 already exists. How would you like to proceed?",
  options: [
    "Merge: add missing topics from legacy config, preserve existing topic customizations",
    "Overwrite: replace entirely with freshly migrated config",
    "Cancel"
  ]
)

Store as merge_mode ("merge", "overwrite", or cancel/exit).

If version != "2.0": treat as overwrite.

Step 0.3: Early exit if nothing to migrate

If no source files found AND no v1.0 target:

Output: "Nothing to migrate. No legacy config files found."
Output: "To create a fresh config, run /sigint:init."
Exit.

Phase 1: Parse Legacy Sources

Step 1.1: Parse project sigint.local.md (if exists)

Read ./.claude/sigint.local.md. The file may use either format:

Format A — YAML frontmatter (between --- delimiters): Extract default_repo, report_format, audiences from frontmatter. Extract markdown body (everything after closing --- separator). Store as local_md_body.

Format B — Markdown sections (## headings with values on next line): Parse ## Report Format, ## Default Repo, ## Audiences headings. The value is the text on the line(s) following the heading. For audiences, split comma-separated values into an array. Store remaining content as local_md_body.

Extract:

default_repo (string or null)
report_format (string or null)
audiences (array or null)

Step 1.2: Parse global sigint.local.md (if migrate_global AND exists)

Same extraction from ~/.claude/sigint.local.md. Store as global_defaults_raw.

Step 1.3: Parse .sigint.config.json v1.0 (if exists)

Read and parse as JSON. If the file is malformed JSON:

Output: "WARNING: .sigint.config.json is not valid JSON — skipping. Will use defaults."
Continue with empty v1_research_config.

If valid, extract research.maxDimensions, research.dimensionTimeout, research.defaultPriorities. Store as v1_research_config.

Step 1.4: Discover existing topics from reports

Glob("./reports/*/state.json")

For each match, read and extract topic_slug (from directory name in glob path) and topic (human-readable name from state.json). Store as discovered_topics.

Phase 2: Build v2.0 Config

Step 2.1: Construct defaults block

"defaults": {
  "default_repo": <project_local_md.default_repo ?? null>,
  "report_format": <project_local_md.report_format ?? "markdown">,
  "audiences": <project_local_md.audiences ?? ["technical"]>
}

Step 2.2: Construct research block

"research": {
  "maxDimensions": <v1_research_config.maxDimensions ?? 5>,
  "dimensionTimeout": <v1_research_config.dimensionTimeout ?? 300>,
  "defaultPriorities": <v1_research_config.defaultPriorities ?? ["competitive", "sizing", "trends"]>
}

Step 2.3: Construct topics block

For each {slug, name} in discovered_topics:

"<slug>": {
  "context_file": "./reports/<slug>/CONTEXT.md"
}

If merge_mode == "merge": preserve all existing topic entries from current v2.0 config; only add newly discovered slugs not already present.

Step 2.4: Assemble complete v2.0 config

{ "version": "2.0", "defaults": ..., "research": ..., "topics": ... }

Phase 3: Plan CONTEXT.md Files

For each discovered topic:

Path: ./reports/{slug}/CONTEXT.md

Content: local_md_body if non-empty, else:

# Research Context: {topic name}

<!-- Add project-specific context, constraints, or background here -->

If CONTEXT.md already exists at that path: mark as "skip — already exists".

Phase 4: Preview and Confirm

Step 4.1: Display migration plan

Sigint Configuration Migration Plan
=====================================

Sources detected:
  {[found] or [not found]} .claude/sigint.local.md (project)
  {[found] or [not found]} ~/.claude/sigint.local.md (global)
  {[found] or [not found]} .sigint.config.json (v1.0)

Target: ./sigint.config.json (v2.0) — {create fresh | merge with existing | overwrite existing}

Topics to register ({count}): {slug list}

Files to write:
  [CREATE or UPDATE] ./sigint.config.json
  {for each new CONTEXT.md: "  [CREATE] ./reports/{slug}/CONTEXT.md"}
  {for each skipped CONTEXT.md: "  [SKIP — exists] ./reports/{slug}/CONTEXT.md"}

Files to back up:
  {for each source: "  {source} → {source}.bak"}

Resolved defaults:
  default_repo:   {value or "not set"}
  report_format:  {value}
  audiences:      {value}
  maxDimensions:  {value}

If dry_run = true:

DRY RUN — no files modified. Remove --dry-run to execute.

Exit after preview.

If dry_run = false:

AskUserQuestion(
  question: "Proceed with migration?",
  options: ["Proceed", "Cancel"]
)

Phase 5: Execute Migration

(Skipped if dry_run = true.)

Step 5.1: Back up legacy files FIRST

Back up before writing anything to ensure no data loss if a subsequent step fails.

If a .bak file already exists at the target path, use a timestamped suffix instead (e.g., .bak.20260402) to avoid overwriting previous backups.

Bash: mv ./.claude/sigint.local.md ./.claude/sigint.local.md.bak  (if existed)
Bash: mv ./.sigint.config.json ./.sigint.config.json.bak  (if existed)
If migrate_global AND ~/.claude/sigint.local.md exists:
  Bash: mv ~/.claude/sigint.local.md ~/.claude/sigint.local.md.bak

Step 5.2: Write CONTEXT.md files

For each topic where CONTEXT.md does not already exist:

Write("./reports/{slug}/CONTEXT.md", content)

Step 5.3: Write sigint.config.json

Write using jq (per Structured Data Protocol):

jq -n \
  --argjson defaults "$DEFAULTS_JSON" \
  --argjson research "$RESEARCH_JSON" \
  --argjson topics "$TOPICS_JSON" \
  '{version: "2.0", defaults: $defaults, research: $research, topics: $topics}' \
  > ./sigint.config.json
jq -e -f schemas/sigint-config.jq ./sigint.config.json > /dev/null

If schemas/sigint-config.jq does not exist, skip schema validation and emit a warning:

WARNING: Schema file schemas/sigint-config.jq not found — skipping validation. Run /sigint:init to generate it.

Step 5.4: Update .gitignore

If .gitignore exists:

Read it. Find a line containing .claude/sigint.local.md:
- If found, use sed via Bash to replace that line with sigint.config.json
- If not found, check if sigint.config.json is already listed. If not, append via Bash:
```
# Sigint local config (contains user-specific settings)
sigint.config.json
```

If .gitignore does not exist:

Create it with:

# Sigint local config (contains user-specific settings)
sigint.config.json

Phase 6: Completion Output

Migration complete (v1.0 → v2.0).

Sources migrated:
  {list of source files that were parsed}

Written:
  sigint.config.json (v2.0)
  {each CONTEXT.md written}

Backed up:
  {each .bak file created}

Settings migrated:
  default_repo:   {value or "not set"}
  report_format:  {value}
  audiences:      {comma-separated list}
  maxDimensions:  {value}

{count} topic(s) registered: {slug list}

Next steps:
  - Review ./sigint.config.json and add per-topic customizations
  - Edit ./reports/{slug}/CONTEXT.md to add project-specific context
  - Run /sigint:init to verify configuration
  - Run /sigint:start <topic> to begin a research session

Agent Skills: Sigint Migrate Skill

Install this agent skill to your local

Skill Files