Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

issue-sync

Sterne3

Forks0

Aktualisiert5. Juli 2026 um 07:23

Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

dvy1987

dvy1987/agent-loom

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	issue-sync
description	Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.
license	MIT
metadata	{"author":"dvy1987","version":"1.0","category":"project-specific","sources":"ci-orchestrator Notifier pattern","resources":{"references":["SYNC-SCHEMA.md","examples.md"]}}

Issue Sync

You mirror create/update/close events between source and target trackers using a stable external-ID map — no duplicate issues.

Hard Rules

Maintain mapping at .agent-loom/issue-sync-map.json — {source_id, target_id, status, last_synced_at}. Never create a target issue without recording the mapping. On update: look up mapping first; create only if absent. Never store API tokens in repo — env vars only. If either side credentials missing, list required env names and stop.

Workflow

Step 1 — Identify source and target

Example: GitHub → Linear, or Linear → GitHub. Confirm direction with user if ambiguous.

Step 2 — Load or init map

Read .agent-loom/issue-sync-map.json. Create {"mirrors":[]} if missing.

Step 3 — Fetch source changes

List open/recently updated issues since last_synced_at (or user-provided window).

Step 4 — Apply to target

Source event	Target action
create	Create issue + append mapping
update status	Update mapped target status
close	Close mapped target

Step 5 — Write map + summary

Persist updated mirrors. Emit sync report.

Gotchas

Title-only matching causes duplicates — always use mapping file.
Bidirectional sync needs conflict policy — default: source wins unless user says otherwise.
Body HTML vs markdown may truncate — sync title + status + link back.

Output Format

## Issue sync — [source] → [target]

Created: N | Updated: N | Closed: N | Skipped (mapped): N
Map: `.agent-loom/issue-sync-map.json`

Errors: [none | list]

Examples

Teaser: 3 new GitHub issues → 3 Linear issues created with github:#42 in description.

Full pairs: references/examples.md

Common Rationalizations

Excuse	Reality
"Match by title"	Titles change; duplicates multiply.
"Skip map file"	Next sync creates duplicates.
"Embed PAT in script"	Tokens leak from repo history.
"Sync everything ever"	Window by last_synced_at — incremental.
"Bidirectional without policy"	Conflicts will corrupt state.

Verification

Mapping file updated
No duplicate target for same source_id
Credentials not written to disk
Sync counts reported

Red Flags

New target issue without map entry
API token in committed file
Full resync without user request

Prune Log

Last pruned: 2026-07-05

Initial release from high-leverage skill spec (Skill 3 family)

Impact Report

Issue sync: [src]→[tgt] | +N ~N -N | Map entries: N

Mehr aus diesem Repository

gleiches Repository

code-review-crsp

dvy1987/agent-loom

Review code changes for correctness, completeness, bugs, edge cases, and quality. Load when the user explicitly asks to review code, check a PR, review a diff, audit recent changes, or verify an implementation matches requirements. Also triggers on "review this code", "check this PR", "review my changes", "code review", "did this implement correctly", "audit this diff", or any explicit request for a formal code review. Do NOT load for "review changes for context" or "review what happened" — those are requests to read code, not to perform a formal review.

2026-07-093

debug-and-fix

dvy1987/agent-loom

Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.

2026-07-093

git-workflow-and-versioning

dvy1987/agent-loom

Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.

2026-07-093

implementation-plan

dvy1987/agent-loom

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

2026-07-093

incremental-implementation

dvy1987/agent-loom

Deliver multi-file changes in thin vertical slices — implement, test, verify, commit, repeat. Load when implementing a feature from a plan, building across more than one file, refactoring, or when tempted to land a large change in one pass. Also triggers on "incremental implementation", "vertical slice", "thin slice", "one slice at a time", "don't do it all at once". Routes single-file fixes to direct execution. Pairs with test-driven-development and git-workflow-and-versioning.

2026-07-093

test-driven-development

dvy1987/agent-loom

Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.

2026-07-093

name	issue-sync
description	Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing GitHub and Linear issues, mirroring ticket status, or keeping two trackers in sync. Also triggers on "issue sync", "sync issues", "mirror issues to", "keep Linear and GitHub in sync", or bidirectional issue tracker updates. Requires API access on both sides — stops if credentials missing.
license	MIT
metadata	{"author":"dvy1987","version":"1.0","category":"project-specific","sources":"ci-orchestrator Notifier pattern","resources":{"references":["SYNC-SCHEMA.md","examples.md"]}}

Issue Sync

You mirror create/update/close events between source and target trackers using a stable external-ID map — no duplicate issues.

Hard Rules

Workflow

Step 1 — Identify source and target

Example: GitHub → Linear, or Linear → GitHub. Confirm direction with user if ambiguous.

Step 2 — Load or init map

Read .agent-loom/issue-sync-map.json. Create {"mirrors":[]} if missing.

Step 3 — Fetch source changes

List open/recently updated issues since last_synced_at (or user-provided window).

Step 4 — Apply to target

Source event	Target action
create	Create issue + append mapping
update status	Update mapped target status
close	Close mapped target

Step 5 — Write map + summary

Persist updated mirrors. Emit sync report.

Gotchas

Title-only matching causes duplicates — always use mapping file.
Bidirectional sync needs conflict policy — default: source wins unless user says otherwise.
Body HTML vs markdown may truncate — sync title + status + link back.

Output Format

## Issue sync — [source] → [target]

Created: N | Updated: N | Closed: N | Skipped (mapped): N
Map: `.agent-loom/issue-sync-map.json`

Errors: [none | list]

Examples

Teaser: 3 new GitHub issues → 3 Linear issues created with github:#42 in description.

Full pairs: references/examples.md

Common Rationalizations

Excuse	Reality
"Match by title"	Titles change; duplicates multiply.
"Skip map file"	Next sync creates duplicates.
"Embed PAT in script"	Tokens leak from repo history.
"Sync everything ever"	Window by last_synced_at — incremental.
"Bidirectional without policy"	Conflicts will corrupt state.

Verification

Mapping file updated
No duplicate target for same source_id
Credentials not written to disk
Sync counts reported

Red Flags

New target issue without map entry
API token in committed file
Full resync without user request

Prune Log

Last pruned: 2026-07-05

Initial release from high-leverage skill spec (Skill 3 family)

Impact Report

Issue sync: [src]→[tgt] | +N ~N -N | Map entries: N