15 04 Review To Tickets
Productivity15-04-review-to-tickets15 04 Review To Tickets is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Convert findings from any review, audit, or analysis into individual tk tickets with proper priority and tagging.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/planning/15-04-review-to-tickets/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/15-04-review-to-tickets, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
15.04 Review-to-Tickets
After any review, audit, or analysis that surfaces issues, create tk tickets for every finding.
When This Applies
Any skill or workflow that produces a report of issues:
- Code review (code-review, review-changes)
- Audits (audit, architectural-analysis, axiom-audit, file-name-wizard)
- Plan checks (check-plan)
- Spec/quality reviews (teams-driven-development, 4-step-program)
Process
- Collect all findings from the review/audit report.
- Create one ticket per finding (or group tightly related findings into one ticket).
- Tag tickets with the source skill and severity.
- Reference the report in each ticket's Links section.
Ticket Format
ID=$(tk create "SHORT DESCRIPTION" \
-t task \
-p PRIORITY \
--tags SEVERITY,SOURCE_SKILL \
-d "## Goal
What needs to be fixed or addressed.
## Source
- Skill: SOURCE_SKILL
- Report: path/to/report.md
- Severity: CRITICAL|HIGH|MEDIUM|LOW
## Details
Exact finding from the report. Include file paths and line numbers.
## Acceptance Criteria
- [ ] Issue is resolved
- [ ] Verification: SPECIFIC CHECK") && tk start $ID
Priority Mapping
| Severity | tk Priority | Action |
|---|---|---|
| CRITICAL | 0 (urgent) | Fix immediately |
| HIGH | 1 | Fix before merge/release |
| MEDIUM | 2 | Fix soon |
| LOW | 3 | Fix when convenient |
Grouping Rules
- One ticket per distinct issue. Don't lump unrelated findings.
- Group related findings if they share the same root cause (e.g., 5 files all missing the same type → one ticket).
- Split large findings if they require different fixes in different areas.
After Creating Tickets
- Close tickets as you fix issues.
- Reference ticket IDs in commits:
t-XXXX: fix description - Log changes via
tinychange.