agentleFS
Sign inStart free
kjnezkjnez/claude-code-django/.claude/skills/ticket/SKILL.md

ticket

Skill177 starsChanged 10 months agoMITView on GitHub

Work on a JIRA/Linear ticket end-to-end: read ticket details, explore codebase, create a branch, implement with TDD, run quality checks, update ticket status, and create a PR. Use when the user provides a ticket ID to implement. Triggers on requests like "/ticket PROJ-123", "work on this ticket", "implement PROJ-123".

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 8

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

    Check linked tickets or epics

    line 16
  2. Distinctive:

    Search for related code

    line 24
  3. Distinctive:

    Follow project patterns (check relevant skills)

    line 36
  4. Distinctive:

    Write tests first (TDD)

    line 37
  5. Distinctive:

    Add comments with progress updates

    line 52
  6. Distinctive:

    Update status (In Progress → In Review)

    line 53
  7. Very specific:

    Create PR with gh pr create

    line 59
  8. Very specific:

    Add ticket ID to PR title: feat(PROJ-123): description

    line 61
  9. Distinctive:

    If you discover an unrelated bug while working:

    line 65
  10. Distinctive:

    Create a new ticket with details

    line 66

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

Ticket Workflow

Work on the ticket ID provided by the user.

Instructions

1. Read the Ticket

Fetch and understand the ticket using JIRA/Linear MCP tools:

  • Get ticket details (title, description, acceptance criteria)
  • Check linked tickets or epics
  • Review any comments or attachments

Summarize: what needs to be done, acceptance criteria, blockers or dependencies.

2. Explore the Codebase

Before coding:

  • Search for related code
  • Understand the current implementation
  • Identify files that need changes

3. Create a Branch

git checkout -b {initials}/{ticket-id}-{brief-description}

4. Implement the Changes

  • Follow project patterns (check relevant skills)
  • Write tests first (TDD)
  • Make incremental commits

5. Run Quality Checks

uv run ruff check .
uv run ruff format .
uv run pyright
uv run pytest

6. Update the Ticket

As you work:

  • Add comments with progress updates
  • Update status (In Progress → In Review)
  • Log any blockers or questions

7. Create PR and Link

When ready:

  • Create PR with gh pr create
  • Link the PR to the ticket
  • Add ticket ID to PR title: feat(PROJ-123): description

8. If You Find a Bug

If you discover an unrelated bug while working:

  1. Create a new ticket with details
  2. Link it to the current ticket if related
  3. Note it in the PR description
  4. Continue with original task

Download now (ZIP)

  • Other versions16 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 16

    1. ConnorGriffin/skills★ 21same name
    2. a-saven/agent-skills★ 2same name
    3. AaravChadha/acstack★ 2same name
    4. gingerminds/claude-skills★ 2same name
    5. HoussemDjeghri/self-review★ 1same name
    6. ilamanov/skills★ 1same name
    7. OHOKAYYEAH/claude-skills★ 1same name
    8. rikilamadrid/lorekeeper★ 1same name
    9. rikilamadrid/pathfinder★ 1same name
    10. tarrragon/claude-skills★ 1same name

    6 more not listed

    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.

  • Used alongsideProjects with it also use orchestrate, handoff and 2 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.
    • varun29ankuSSkill

      orchestrate

      This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.

      Also in 3 projects that use this

    • MicrosoftSkill

      handoff

      Compact the current conversation into a handoff document for another agent to pick up.

      Also in 5 projects that use this

    • GoogleSkill

      prototype

      Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

      Also in 3 projects that use this

    • GoogleSkill

      tdd

      Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

      Also in 3 projects that use this

  • In this repository16 other files it gives its agents.

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