agentleFS
neomjsneomjs/neo-agent-skills/.agents/skills/ticket-intake/SKILL.md

ticket-intake

Skill11 starsChanged yesterdayMITView on GitHub

Pre-execution reflection gate for GitHub issues; use before branching or modifying code on any assigned/claimed ticket (full gate if peer-authored, or prescription/drift probe if self-authored).

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you are an agent tasked with executing a ticket or issue whose authoring you did not see, you MUST NOT begin executing Git branch …

    line 8

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ticket Intake Skill

If you are an agent tasked with executing a ticket or issue whose authoring you did not see, you MUST NOT begin executing Git branch commands or writing code before running the Pre-Execution Reflection Gate (architectural validation, negative ROI calculation, and duplicate sweeps).

You MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/ticket-intake/references/ticket-intake-workflow.md before proceeding. Or, if you already have the payload in context, proceed directly to its directives.

Ticket you authored yourself: read references/self-authored-carve.md FIRST — a ticket authored this session is exempt EXCEPT the prescription check; one authored in an earlier session runs a cheap drift probe instead (never an exemption you judge for yourself).

Download now (ZIP)

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.