rag-change-impact
Skill1 starsChanged 3 months agoMITView on GitHub
Use when a D:/RAG source file changes, a new version is provided, or the user asks what RC, tests, packets, or downstream assets may be impacted.
In this repository22 other files it gives its agents.
- analysis-skillSkill
- auto-testcase-generatorSkill
- create-agent-skillSkill
- create-skillSkill
- development-systemSkill
- domain-modelingSkill
- figma-rest-syncSkill
- grill-systemSkill
- grill-with-docsSkill
- rag-downstream-handoffSkill
- rag-governanceSkill
- rag-intakeSkill
- rag-querySkill
- rag-schemaSkill
- rag-structure-fidelitySkill
- rag-systemSkill
- researchSkill
- session-handoffSkill
- skill-packagerSkill
- task-understanding-routerSkill
- ui-testSkill
- write-requirements-prdSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 10
Never update RC automatically from changed source material.
- Distinctive: line 11
Treat new source versions as candidate evidence until user review.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rag Change Impact
Operating Rules
- Never update RC automatically from changed source material.
- Treat new source versions as candidate evidence until user review.
- Record impacted RC, conflicts, tests, packet fixtures, and downstream consumers.
Workflow
- Compare source identity, hash, version, and material status.
- Identify impacted evidence, knowledge units, conflicts, RC, and downstream packets.
- Produce a Change Impact Packet under
D:/RAG/06_governance/changesorD:/RAG/reports. - Mark unresolved impacts as
need-review.
Validation
Run python D:\RAG\scripts\validate_rag_mvp.py.
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.

