tidd

A Ticket-driven Development setup guide that enforces the rule “No Ticket, No Commit.” A ticket is a trackable work item, such as a GitHub Issue, Jira item, or Linear task.

In plain words
What is it for?
Use it to install a pre-tool hook, require ticket numbers in commit messages or branch names, and configure patterns and exceptions for GitHub Issues, GitLab, Jira, Linear, or Trello.
Why use it?
It links code changes to the reason they were made and prevents commits or branches from losing that context. This makes changes easier to trace and review.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/roboco-io/plugins/tidd
Any agent
npx skills add roboco-io/plugins --skill tidd
Clone the repo
git clone --depth 1 https://github.com/roboco-io/plugins

Made for: Claude Code, Codex.

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 948 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00076 $0.00948
Opus 5 $0.00038 $0.00474
Sonnet 5 $0.00015 $0.00190
Haiku 4.5 $0.00008 $0.00095

Measured yesterday against content hash dd6788b84d6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tidd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

The scan reads SKILL.md. This mod also ships 1 executable file (hooks/validate.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/workflow/skills/tidd/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TiDD — Ticket Driven Development

No Ticket, No Commit. 모든 코드 변경은 반드시 추적 가능한 티켓과 연결되어야 합니다.

원칙

  1. 모든 변경에는 티켓이 있어야 한다 — 티켓 없이 코드를 변경하지 않는다
  2. 커밋 메시지 또는 브랜치명에 티켓 번호가 포함되어야 한다 — 둘 중 하나만 만족하면 통과
  3. 티켓은 변경의 맥락(Why)을 담는다 — 코드는 What, 티켓은 Why

지원 티켓 시스템

시스템 패턴 예시 정규식
GitHub Issues #123, org/repo#456 #[0-9]+
GitLab Issues #123, group/project#456 #[0-9]+
Jira PROJ-123, DEV-456 [A-Z][A-Z0-9]+-[0-9]+
Linear ENG-123, FE-456 [A-Z][A-Z0-9]+-[0-9]+
Trello TRELLO-123 [A-Z][A-Z0-9]+-[0-9]+

기본 패턴: #[0-9]+ 또는 [A-Z][A-Z0-9]+-[0-9]+

설치

1. 훅 스크립트 권한 설정

chmod +x plugins/workflow/skills/tidd/hooks/validate.sh

2. Claude Code 설정에 훅 등록

프로젝트의 .claude/settings.json에 추가:

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "command": "/path/to/plugins/workflow/skills/tidd/hooks/validate.sh"
      }
    ]
  }
}

: 절대 경로 대신 플러그인 설치 경로 기준으로 설정하세요.

3. (선택) 프로젝트 커스터마이즈

프로젝트 루트에 .tidd.json 생성:

{
  "patterns": ["#[0-9]+", "[A-Z][A-Z0-9]+-[0-9]+"],
  "branchPatterns": ["[A-Z][A-Z0-9]+-[0-9]+", "issue-[0-9]+"],
  "exemptBranches": ["main", "master", "develop", "release/*", "hotfix/*"],
  "exemptTypes": ["merge", "revert"]
}

설정 상세는 configuration.md를 참조하세요.

동작 방식

git commit 감지
    │
    ├─ merge/revert 커밋? ──→ 통과
    │
    ├─ exempt 브랜치? ──→ 통과
    │
    ├─ 커밋 메시지에 티켓 번호? ──→ 통과
    │
    ├─ 브랜치명에 티켓 번호? ──→ 통과
    │
    └─ 차단: "No Ticket, No Commit!"

커밋 메시지 예시

# GitHub Issues
git commit -m "feat(auth): add OAuth2 support #123"

# Jira
git commit -m "feat(auth): add OAuth2 support PROJ-123"

# 본문에 포함해도 OK
git commit -m "feat(auth): add OAuth2 support

Resolves #123"

브랜치명 예시

# 브랜치명에 티켓 번호가 있으면 커밋 메시지에는 없어도 통과
git checkout -b feature/PROJ-123-oauth-login
git commit -m "feat(auth): add OAuth2 support"  # 통과!

Read the full file on GitHub · 108 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 108 lines · 76 tokens per session scan A dd6788b84d6d

Subscribe to this mod's changes

tidd is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 948 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens