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

implement-ticket

Skill0 starsChanged 5 months agoNo licenceView on GitHub

Quy trình dev thực hiện một ticket từ bộ gap-analysis (docs-workspace/gap/08-tickets.md hoặc docs/gap/08-tickets.md) hoàn toàn trong terminal: đọc ticket + context pack → lập kế hoạch và chờ dev duyệt → code theo ràng buộc kiến trúc → build/test/lint → tự review theo Definition of Done → cập nhật docs/audit → bàn giao sang bước tạo MR. LUÔN dùng skill này khi người dùng nói: "làm ticket T-xx", "implement ticket", "code ticket", "làm task T-xx", "bắt đầu ticket", "tiếp tục ticket", hoặc tham chiếu mã ticket dạng T-xx / REQ-xx kèm ý định triển khai. Dùng cho cả ticket backend (API/logic) và frontend (giao diện theo ảnh Figma).

  • Reads credentials
  • Commits and pushes

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

Create a free account to mount

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