agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/attach-session-to-jira/SKILL.md

attach-session-to-jira

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Attach the current AI session context to a Jira issue as a formatted comment. Useful for investigation, audit trail, handoff, debugging. Use when user says "attach session to Jira", "document on Jira", or "export context to AAP-XXXXX".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    If invalid: raise error with expected format

    line 23
  2. Distinctive:

    If "No Active Session" or "Session Not Found": raise error "Call session_start() first"

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Attach Session to Jira

Exports AI session context and attaches it to a Jira issue. Includes session metadata, summary stats, key actions, related issue keys, and optional full transcript.

Inputs

InputTypeDefaultPurpose
issue_keystringrequiredJira issue key (e.g., AAP-12345)
session_idstring""Session ID to export. Empty = active session
include_transcriptboolfalseInclude full conversation transcript (collapsible)

Workflow

1. Validate Issue Key

  • Format: ^[A-Z]+-\d+$ (e.g., AAP-12345)
  • If invalid: raise error with expected format

2. Get Session Info

  • session_info(session_id=session_id) — Get current/requested session
  • If "No Active Session" or "Session Not Found": raise error "Call session_start() first"
  • Extract session_id from output if present

3. Attach to Jira

  • jira_attach_session(issue_key=validated_issue_key, session_id=session_id, include_transcript=include_transcript)

4. Log

  • memory_session_log(action="Attached session context to {issue_key}", details="Include transcript: {include_transcript}")

Output Format

{attach_result}

---

## Next Steps

1. **View on Jira:** [AAP-12345](https://issues.redhat.com/browse/AAP-12345)
2. **Export locally:** session_export_context() for markdown/JSON
3. **Share with team:** Link the Jira issue in Slack or email

Error Handling

PatternMessage
Invalid issue keyExpected AAP-12345 format. Got: {input}
No active sessionRun session_start() first
Failed to add commentCheck JIRA_JPAT, issue exists, VPN. Try jira_view_issue()

Key MCP Tools

  • session_info, jira_attach_session, memory_session_log

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free