agentleFS
Sign inStart free
fboulnoisfboulnois/skills/implement-ticket/SKILL.md

implement-ticket

Skill1 starsChanged 4 days agoMITView on GitHub

Implement a JIRA ticket end-to-end, review it with Claude and Codex until clean, and split it into local stacked PR branches. Use when asked to implement or complete a ticket.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use thermo-nuclear-code-quality-review, implement-spec and 8 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.
  • jaydubya818Skill

    thermo-nuclear-code-quality-review

    Use when the user requests an intentionally strict maintainability review.

    Also in 3 projects that use this

  • AWSSkill

    implement-spec

    Implement the result of /to-spec and /to-tickets in code.

    Also in 3 projects that use this

  • GoogleSkill

    to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    Also in 3 projects that use this

  • GoogleSkill

    to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    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 4 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

  • +4 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

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

    Read the JIRA ticket the user specified, treating any suggested implementation as a hint.

    line 9
  2. Very specific:

    Run /commit-pr on each branch diffed against its parent and report the results.

    line 13

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

Implement JIRA Ticket

  1. Read the JIRA ticket the user specified, treating any suggested implementation as a hint. Complete the ticket with tests in a worktree from the default branch. Run all later steps there.
  2. Split the work into a series of atomic commits. Ensure the commit subject is 50 characters or fewer, uses imperative mood, and follows the conventional commit style with no scope, body, or trailer. Describe the change, not a file list.
  3. Cross-check the implementation with both Claude and Codex using parallel subagents, running a code review and a security review in each, with appropriate skills if available. The other agent may be found with command -v $t || find ~/.vscode*/extensions -type f -name $t -perm -u+x 2>/dev/null | sort -V | tail -1; stop if it is unavailable. Verify each finding and discard false positives. Fix all confirmed high and medium findings. Fix a low finding only if the fix is small and local and doesn't change behavior or design. Fold each fix into the commit it belongs to. Repeat until a pass returns no new high or medium findings.
  4. Split the commits into a stack of local PR branches, but do not push. Split only between commits, and keep each branch's diff against its parent under 500 changed lines (additions plus deletions, tests included). Each branch must pass lint and tests on its own.
  5. Run /commit-pr on each branch diffed against its parent and report the results.

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