jira-administration
Skill26 starsChanged 10 days agoMITView on GitHub
Run bounded Jira administration workflows for project Components or Atlassian instance migration. Use for jira-components, sync Jira components, jira-instance-migration, changed Jira URL, or repoint Jira. Both modes are sealed behind read-first analysis and explicit user approval before any Jira, credential-session, or repository mutation.
- Reads credentials
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acliSkill
- agentic-qa-coreSkill
- agentic-qa-onboardSkill
- bug-screenshot-annotationSkill
- business-api-contextSkill
- business-data-contextSkill
- business-domain-contextSkill
- business-e2e-contextSkill
- evidence-artifactSkill
- exploratory-testingSkill
- framework-developmentSkill
- git-flow-masterSkill
- infra-contextSkill
- iql-contextSkill
- judgment-daySkill
- orca-orchestrationSkill
- project-contextSkill
- project-discoverySkill
- pr-review-leadSkill
- regression-testingSkill
- session-handoffSkill
- shift-left-testingSkill
- sprint-conductorSkill
- sprint-testingSkill
- test-automationSkill
- test-documentationSkill
- test-framework-adaptationSkill
- xray-cliSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
If the mode is unclear, ask.
- Distinctive: line 32
Read-first on every mutation: inspect the live state before authoring any plan.
- Distinctive: line 37
Run only the selected reference's verification steps.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Jira Administration
Mode routing
Choose exactly one mode and load only its reference: the first token of $ARGUMENTS when it names a mode below (/jira-administration components BK ../bunkai), otherwise ask. The former jira-components and jira-instance-migration command names survive as trigger phrases only.
| Mode | Trigger phrases | Reference |
components | jira-components, reconcile/sync Jira Components | references/components.md |
instance-migration | jira-instance-migration, changed/repoint Jira instance | references/instance-migration.md |
If the mode is unclear, ask. Never combine both modes in one run.
Compact Rules
The sealed mutation contract. Binding on every run of either mode:
- Exactly ONE mode per run:
components(references/components.md) orinstance-migration(references/instance-migration.md). Load only that mode's reference. Never combine the two, never fall through into the other. - Mode unclear → ASK. Do not infer one from a bare "fix Jira" / "sync Jira" request.
- Load
/aclibefore any Jira operation. Load other tool-owner skills only when the selected reference requires them. - Missing MCP or Jira credentials = HARD STOP (
AGENTS.mdCritical Rule #10). Name the exact env var, point at.env/.env.example, ask for an agent-session restart. No workaround, no partial run. - Read-first on every mutation: inspect the live state before authoring any plan. Nothing is created, applied, deleted, or repointed without the user's explicit approval given inside the same run.
components: derive and inspect → author the plan file → dry-run → WAIT for explicit approval → only then--apply.instance-migration: resolve and confirm BOTH instances → audit and verify reachability → WAIT for explicit approval → only then change files or theaclisession. That session lives at~/.config/acliand is machine-global: re-login repoints every repo on the host, not just this one.- The Atlassian host lives in
.agents/project.yaml→issue_tracker.atlassian_urland NOWHERE else locally. A staleATLASSIAN_URLin.envor the process environment is contamination to DELETE, never to update — a second copy is what goes stale. - Template-repo carve-out: if
.agents/project.yaml→project.project_nameisnull, the repo is an un-onboarded template. Leaveatlassian_urlandproject_keynull, say so in the report, and never manufacture a commit to hide the emptiness. - Run only the selected reference's verification steps. Never run the other mode's.
- Mode from
$ARGUMENTS: when its first token matches a mode in the Mode routing table, that token IS the mode and the rest is forwarded to it unchanged. No matching first token → ASK which mode.
Read full SKILL.md when: the mode is ambiguous, a dry-run diff or migration audit looks wrong, or you need the selected reference's step-by-step phases and verification list.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

