What problem does it solve? Jira administration tasks like syncing project Components to a codebase's real modules or repointing a repository after an Atlassian site migration are error-prone: wrong component names orphan issues, and stale custom-field IDs silently write data into the wrong fields. This Skill runs both operations as read-first, approval-gated workflows so nothing mutates Jira, credentials, or repository files without explicit user consent. ## Core Features & Use Cases - Components mode: Derives functional modules from the target app's source and backlog, diffs them against live Jira Components, and drives scripts/sync-jira-components.ts through a user-approved plan file with dry-run before --apply. - Instance-migration mode: Repoints .agents/project.yaml, cleans stale ATLASSIAN_URL contamination, re-authenticates the machine-global acli session, and regenerates the field, workflow, and link-type catalogs whose IDs the migration invalidated. - Use Case: After your company moves from oldsite.atlassian.net to newsite.atlassian.net, run the migration mode to audit every reference, verify the new instance is reachable, regenerate catalogs, and prove each custom-field ID now maps to the correct field before committing. ## Quick Start Ask the agent to run jira-administration in components mode to sync my Jira project components, or in instance-migration mode with the old and new Atlassian hosts to repoint this repository.
