Skip to content
Agentmart
Submit a tool

ticket-format

Use when creating, drafting, or grooming a Linear or Rox ticket in this repo.

Skill by agisota

IndexedMIT★ 3
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/agisota-ticket-format

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when creating, drafting, or grooming a Linear or Rox ticket in this repo. Defines the canonical three-section structure.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/ticket-format

What's inside

Skill name
ticket-format
Description
Use when creating, drafting, or grooming a Linear or Rox ticket in this repo. Defines the canonical three-section structure.
License
MIT
Instructions
21 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Ticket Format

## Context
2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused.

## References
Where the ticket came from. Omit section if none.

| Source | Who | Link | Date |
|--------|-----|------|------|
| Slack #feedback | @alice | [thread](…) | 2026-05-10 |

## Implementation notes
Agent-groomed. Leave empty if you don't have codebase context — a later grooming pass will fill it in. When you do fill it in, use these sub-headings and skip what doesn't apply:

- `### Files` — `path:line` + why relevant
- `### Approach` — one paragraph
- `### Related code` — similar patterns in the repo
- `### Gotchas` — constraints, prior incidents

From agisota/old-one, MIT.

More from agisota/old-one

Signals

Stars
3
Forks
1
Open issues
139
Last commit (this folder)
Jun 7, 2026 (4 months ago)
Last release
Jun 27, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/agisota/old-one
Website
agisota.github.io/old-one/
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from agisota

Cite this page

ticket-format skill. Agent Mart. https://agentmart.dev/skills/agisota-ticket-format (last updated 2026-10-24)