sync-jira
Skill1 starsChanged 42 days agoAGPL-3.0View on GitHub
Sync Jira issues into TARS. Trigger on "sync jira", "pull my jira tickets", "ingest PROJ-123", "sync everything under <epic>". Default scope is issues assigned to me since the watermark; also fetches concrete issue keys or an epic's children on demand. Fetches via the Atlassian Rovo MCP and stores via the tars CLI so provenance, dedup, and the cursor stay deterministic.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- askSkill
- captureSkill
- digestSkill
- end-of-daySkill
- gardenerSkill
- promoteSkill
- sync-allSkill
- sync-githubSkill
- sync-gmailSkill
- sync-granolaSkill
- sync-slackSkill
- tasksSkill
- trackSkill
The file
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.