atlassian
Skill2 starsChanged 38 days agoMITView on GitHub
Run Bitbucket Cloud, Jira and Confluence work through atlassian-cli. Use for Bitbucket PRs, stacks, pipelines and merges; Jira issues, links, comments, transitions and a board; Confluence pages for specs and ADRs; and CLI setup.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- razbakov/skillstheir own version, first seen Oct 17, 2026
- nordz0r/skillstheir own version, first seen Oct 15, 2026
- dbhq-uk/atlassian-skilltheir own version, first seen Sep 25, 2026
- sanjay3290/ai-skillstheir own version, first seen Jul 6, 2026
- sanjay3290/atlassian-skilltheir own version, first seen Mar 4, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- sanjay3290/ai-skills★ 452same name
- nordz0r/skills★ 8same name
- razbakov/skills★ 4same name
- dbhq-uk/atlassian-skill★ 0same name
- sanjay3290/atlassian-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auditSkill
- code-qualitySkill
- commit-expertSkill
- create-issueSkill
- create-prSkill
- debugSkill
- defineSkill
- deliverSkill
- final-reviewSkill
- gherkinSkill
- githubSkill
- handoffSkill
- plainSkill
- second-opinionSkill
- senior-technical-writerSkill
- testingSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Every product goes through atlassian-cli 0.10.0 or later, with -f json when you read the output.
- Distinctive: line 15
A board is optional: Follow Board.
- Distinctive: line 16
Offer to record the tracker: When you had to ask or infer the Jira project, board or statuses, offer to add them to the project's …
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Atlassian
Every product goes through atlassian-cli 0.10.0 or later, with -f json when you read the output. Where a command lacks a field, atlassian-cli <bb|jira|confluence> api <path> calls the REST API with the stored credentials.
Rules
- Resolve project settings. Start with the project's instructions, which may name the Jira project, the board and its statuses. Read the CLI profile, repository configuration and contribution guidance for the workspace, repository, Jira project and Confluence space. Read product settings for issue types and merge methods. When several targets remain, use the one recent comparable work uses.
- Ask before you publish, unless the user asked for that exact action, or the board mapping already approves the transition. Pushing, creating or editing PRs, issues, pages and comments, transitions and merging all publish.
- A board is optional. Follow Board.
- Offer to record the tracker. When you had to ask or infer the Jira project, board or statuses, offer to add them to the project's instructions so the next agent reads them. Edit that file only after the user agrees.
- Keep tokens in the CLI's stored profile or an environment variable.
- Use scratch files outside the tree for PR descriptions and issue and page bodies, so they are never committed.
References
| Task | Read |
| Install the CLI, create tokens, log in, check permissions | references/setup.md |
| Pull requests, stacks, reviews, pipelines, merging | references/bitbucket.md |
| Jira issues: draft, create, link, comment, transition | references/jira.md |
| Move an issue on a board | references/jira.md |
| Confluence pages: concepts, specs, ADRs, RFCs | references/confluence.md |
Board
A Jira board is a view of issues in a project. Creating an issue does not need one. With none, skip it. With one, use it; with several, ask which.
- Unless the project's instructions give the board and statuses, list them (jira.md: Board) and ask once which status is in progress, which is in review, and which is done. Skip a step the user leaves unset. That answer approves the later transitions.
- Confirm the issue shows on the board after creating it: a Scrum board puts it in the backlog, and a board's filter can leave it out.
- Read the current status (jira.md: Board). Set in progress before implementation starts, and assign the logged-in user (jira.md: Other commands), so other agents see the issue is taken. Set in review when its PR opens, and done when that PR merges, not when work on the issue finishes.
Script
scripts/create-issues.mts validates Jira drafts and, with --apply, creates and links them. Run it with Node 22.6 or later:
node --experimental-strip-types <this skill's folder>/scripts/create-issues.mts <file.md | folder> --project <KEY> [--apply]Without --apply it only validates and prints what it would create. <issue script> in the references means this command.
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.