change-tracking
Skill0 starsChanged 36 days agoApache-2.0View on GitHub
Create or find the ticket a piece of work belongs to, per this repository's change-tracking rules. GitHub Issues only, for now.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dotnet/efcoretheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dotnet/efcore★ 15ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Files
Change tracking per this repository's rules. GitHub Issues is the only supported tracker today; for anything else, say so and stop.
Find the rules
First .agentics.yaml at the repository root: change-tracking.tracker
is github-issues or none - with none there is nothing to create and
this skill says so and stops; source-control.mode says whether creating a
ticket asks first. Then read the rule in the first location that exists,
then the tracker file it names. Never work from memory.
| Rule | Initialized repository | dc-agentics toolkit |
| change tracking - the ticket rule, the setting, the initialization exception, boards; names the tracker file | agentics/rules/change-tracking/change-tracking.md | repo/payload/agentics/rules/change-tracking/change-tracking.md |
Actions from $ARGUMENTS
| Argument | Do | Where the procedure is |
new "<what and why>" | create the ticket and report its number | change tracking, Before any work; tracker file, Tickets |
find <#n | words> | show the ticket, or the tickets matching the words | tracker file, Tickets |
Always
A ticket is a sentence of intent, not a design document. Creating one is a
host action: it follows source-control.mode in the source-control rules,
For an agent. Nothing is invented that the user did not give - not the
ticket's intent, not which ticket the work belongs to.
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
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.