All authors
Claude Skills by thientranhung
github.com/thientranhung17 skills0 installs0 views
- Batch TriageTriage an inherited backlog in one pass — many existing issues at once, rather than one new item at a time. Classifies each by reading its own content and the code it names, dedupes, marks the stale, and produces tracker tickets with labels and blocking edges. Invoke by name when adopting a repo that arrives with a backlog.Votes: 0GitHub stars: 3
- Bootstrap GlossarySeed CONTEXT.md with the domain terms the code already uses, each term carrying the file it was read from and marked unreviewed until the owner confirms it. Invoke by name at bootstrap on an existing codebase, instead of a fifty-question domain interview. Extracts vocabulary from code; it does not invent definitions.Votes: 0GitHub stars: 3
- Codex ArmInvocation mechanics for the cross-vendor arm — the Codex pass Thomas fires over a completed artifact. Covers the runtime invocation, argv and quoting gotchas, intent-loaded focus text, failover, and where the outcome is recorded. The BUILDER fires the ticket arm from its own worktree; Thomas fires spec and slice from the base checkout. Never Rin. Cadence lives in thomas.md and builder.md.Votes: 0GitHub stars: 3
- Codex Claude ArmARM ONLY — the Claude pass a Codex root fires over a completed artifact: the Builder fires it per ticket from its own worktree, Thomas fires it at spec and at slice close. Covers the isolated worktree, the read-only allowlist, cleanup order, and recording. This skill never dispatches a reviewer and never hosts a gate; a Codex root cannot host the gate (see review-with-rin). Use on a Codex root when an artifact is committed and ready for its arm.Votes: 0GitHub stars: 3
- Dispatch Qa WalkThomas-only recipe to dispatch QA's product walk — the gate that uses the running system instead of reading the diff. Arrange an app at the reviewed SHA in its own worktree, pack the plan inputs (persona, data state, surfaces including unchanged ones, contracts, journeys, the previous verified-clean list), collect the report, then stop the app. Use before a PR, a merge or a release.Votes: 0GitHub stars: 3
- Dispatch Ticket ClaudeClaude Code-specific dispatch protocol. Covers the astragentic-dispatch mod (the pane records itself, runs its brief, reports its turn end), the launcher matrix, pre-dispatch verification, and Claude runtime facts. Read dispatch-ticket for the shared protocol.Votes: 0GitHub stars: 3
- Dispatch Ticket CodexCodex-specific launcher and verification for dispatch-ticket. Covers the launcher matrix, the in-repo role instruction files, project-local custom agents and hooks, the two-step herdr launch, and Codex-specific runtime facts. Read dispatch-ticket for the shared protocol.Votes: 0GitHub stars: 3
- Dispatch Ticket OpencodeOpenCode-specific launcher and verification for dispatch-ticket. Covers the launcher matrix, pre-dispatch adapter verification, herdr agent start template, and measured opencode runtime facts (idle fabrication, transcript limits, effort unreachable). Read dispatch-ticket for the shared protocol.Votes: 0GitHub stars: 3
- Dispatch TicketDispatch one claimed ticket as a visible Herdr pane — one Builder, one worktree, one branch, one pane. Use when launching a Builder, a Shaper, QA or Rin into a pane. Pair with dispatch-ticket-claude, dispatch-ticket-codex or dispatch-ticket-opencode for the launcher.Votes: 0GitHub stars: 3
- Github Issue TrackerOperating mechanics for a project whose tracker is GitHub Issues — status as labels, the claim, native dependencies keyed by database id, the frontier loop, and the Projects board mirror. Load it when the project's docs/agents/issue-tracker.md names GitHub. Read tracker-contract.md for what the pipeline requires of any tracker.Votes: 0GitHub stars: 3
- Jira Issue TrackerOperating mechanics for a project whose tracker is Jira — status as numbered transitions, cloudId and JQL quoting, issue links and their invertible direction, whole-field description writes, and what only a human can change. Load it when the project's docs/agents/issue-tracker.md names Jira. Read tracker-contract.md for what the pipeline requires of any tracker.Votes: 0GitHub stars: 3
- Legacy TestingHow to get existing untested code under test — characterisation tests that pin current behaviour, and creating a seam before TDD can attach. Use when you need to change code that has no tests, when the code under a ticket has no seam to test through, when a test would require the whole system to run, or when tdd cannot start because there is nothing to write a test against.Votes: 0GitHub stars: 3
- Linear Issue TrackerOperating mechanics for a project whose tracker is Linear — native states and relations, the claim protocol where assignee cannot hold a Builder identity, wayfinding primitives, and the free-tier issue ceiling that stops a pipeline outright. Load it when the project's docs/agents/issue-tracker.md names Linear. Read tracker-contract.md for what the pipeline requires of any tracker.Votes: 0GitHub stars: 3
- Reconcile TrackerReconcile the tracker against git — detect tickets whose recorded state contradicts what actually merged, plus stale claims. Read-only; it reports drift and never writes to the tracker. Use at session start, immediately after every merge, and whenever the tracker's accuracy is in question.Votes: 0GitHub stars: 3
- Review With RinThomas-only recipe to run Rin's milestone gate as an observable Herdr gate pane — brief, dispatch, collect the report, classify. Use when a spec is finalized, a ticket/PR or epic closes, or the owner asks for a Rin review.Votes: 0GitHub stars: 3
- UntangleA refactor path for code too tangled for improve-codebase-architecture — where there are no module boundaries to improve, everything imports everything, and a clean restructure would be one enormous unreviewable change. Use when a refactor cannot be scoped, when improve-codebase-architecture has nothing to work with, or when a change's blast radius keeps growing the more you read.Votes: 0GitHub stars: 3
- Codex ArmInvocation mechanics for the cross-vendor arm on a Claude root — the Codex pass Thomas fires over a completed artifact. Covers the runtime invocation, argv and quoting gotchas, intent-loaded focus text, failover, and where the outcome is recorded. The BUILDER fires the ticket arm from its own worktree; Thomas fires spec and slice from the base checkout. Never Rin. Cadence lives in thomas.md and builder.md.Votes: 0GitHub stars: 3