agentleFS
GavinGreenwoodGavinGreenwood/agentic-workflow-template/.agents/skills/capture/SKILL.md

capture

Skill5 starsChanged 44 days agoMITView on GitHub

Create a Jira ticket from the conversation, then commit related changes. Use when the user asks to capture the work, or to create, raise or log a ticket for something discussed (e.g. "go create that ticket for me").

  • Reads credentials

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly, ingest and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 8 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 6 projects that use this

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 4 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check that JIRA_BASE_URL, JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_ACCOUNT_ID are set in .env.

    line 12
  2. Distinctive:

    If the conversation is fixing broken/incorrect behaviour → Bug

    line 16
  3. Distinctive:

    If the conversation is adding new functionality → Story

    line 17
  4. Very specific:

    If JIRA_BOARD_ID is set in .env, move the ticket onto the active board:

    line 51
  5. Distinctive:

    Only when the ticket is the work in hand.

    line 62
  6. Distinctive:

    Check git status. If there are modified/untracked files relevant to what was discussed:

    line 82
  7. Distinctive:

    Commit with the ticket key and a concise message following CONTRIBUTING.md conventions:

    line 85
  8. Distinctive:

    If there are no changes, skip the commit and confirm the ticket was created.

    line 89

“Common” is measured: kept by at least 6 in 10 of the 58 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.

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

Capture conversation to Jira + commit

Review the full conversation so far and do the following:

Step 1 — Verify credentials

Check that JIRA_BASE_URL, JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_ACCOUNT_ID are set in .env. If any are missing, stop and ask the user to add them. Source .env before all Jira API calls.

Step 2 — Determine issue type

  • If the conversation is fixing broken/incorrect behaviour → Bug
  • If the conversation is adding new functionality → Story
  • Otherwise → Task

Step 3 — Create the Jira ticket

source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
  -X POST "$JIRA_BASE_URL/rest/api/3/issue" \
  -H "Content-Type: application/json" \
  -d "{
    \"fields\": {
      \"project\": { \"key\": \"$JIRA_PROJECT_KEY\" },
      \"issuetype\": { \"name\": \"<Bug|Story|Task>\" },
      \"summary\": \"<concise summary of what was discussed/fixed>\",
      \"description\": {
        \"type\": \"doc\",
        \"version\": 1,
        \"content\": [{
          \"type\": \"paragraph\",
          \"content\": [{
            \"type\": \"text\",
            \"text\": \"<brief description: what the problem was, what was done, any relevant context>\"
          }]
        }]
      },
      \"assignee\": { \"accountId\": \"$JIRA_ACCOUNT_ID\" }
    }
  }"

Capture the ticket key from the response key field (e.g. PROJ-999).

Step 4 — Move onto the active board

If JIRA_BOARD_ID is set in .env, move the ticket onto the active board:

source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
  -X POST "$JIRA_BASE_URL/rest/agile/1.0/board/$JIRA_BOARD_ID/issue" \
  -H "Content-Type: application/json" \
  -d "{\"issues\": [\"<TICKET_KEY>\"]}"

Step 5 — Move ticket to In Progress

Only when the ticket is the work in hand; a follow-up or deferred ticket stays in To Do.

First, get available transitions:

source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
  "$JIRA_BASE_URL/rest/api/3/issue/<TICKET_KEY>/transitions"

Find the transition whose name matches "In Progress" (case-insensitive). Use its id to apply it:

source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
  -X POST "$JIRA_BASE_URL/rest/api/3/issue/<TICKET_KEY>/transitions" \
  -H "Content-Type: application/json" \
  -d '{"transition": {"id": "<transition-id>"}}'

Step 6 — Commit changes (if any)

Check git status. If there are modified/untracked files relevant to what was discussed:

  • Stage the relevant files
  • Commit with the ticket key and a concise message following CONTRIBUTING.md conventions:
    • Format: <TICKET_KEY>: <type>: <short description>
    • Types: fix, feat, refactor, chore

If there are no changes, skip the commit and confirm the ticket was created.

Step 7 — Report back

Tell the user:

  • The ticket key, summary, and link: $JIRA_BASE_URL/browse/<TICKET_KEY>
  • Whether a commit was made (and the commit message if so)

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.