source-control
Skill0 starsChanged 34 days agoApache-2.0View on GitHub
Start work on a ticket with a correctly named, issue-linked branch; commit; open a pull request; or apply the repository's merge settings - all per this repository's source-control and change-tracking rules. GitHub only, for now.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- maroffo/claude-forgetheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- maroffo/claude-forge★ 17same 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
Source control per this repository's rules. GitHub is the only supported host today; for anything else, say so and stop.
Find the rules
First .agentics.yaml at the repository root: its source-control.mode
(auto | local | manual; absent = manual) decides which of the steps
below run without asking and which stop for a yes - the table is in the
source-control rules, For an agent. Then read each rule in the first
location that exists, then the host file the source-control rules name. Never
work from memory.
| Rule | Initialized repository | dc-agentics toolkit |
| source control - branches, commits, size, opening, review, merge, agent guardrails; names the host file | agentics/rules/source-control/source-control.md | repo/payload/agentics/rules/source-control/source-control.md |
| change tracking - the ticket that must exist first; 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 |
publish | put a local repository that has no remote on the host | host file, Publishing a repository |
start <#issue | "description"> | ensure a ticket exists (/change-tracking new when it does not), create the linked branch, switch to it | change tracking, Before any work; tracker file, Tickets |
commit | stage what the user indicates and commit | source control, Commits |
pr | open a draft pull request from the template | source control, Opening a change request; host file, Pull requests |
setup | apply the merge settings and the default-branch ruleset once | host file, Repository settings |
Always
The Guardrails an agent must not skip and For an agent sections of the source-control rules apply to every mode - branch confirmed before every commit, nothing side-effecting run to diagnose, the command shown before anything is created on the host, nothing invented that the user did not give.
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.