serejarisserejaris/ris-claude-code/AGENTS.md

ris-claude-code

AGENTS.md243 starsChanged 3 months agoMITView on GitHub

Collection of Claude Code customizations: skills, statusline, hooks. ALWAYS update BOTH READMEs when releasing: - README.md (English) and README.ru.md (Russian) - Adding/removing skills → update skills list in both READMEs - Adding/removing any component → update corresponding section in both READMEs - Release without README updates = incomplete release - Public repo hygiene changes must keep SECURITY.md, CODE_OF_CONDUCT.md, issue templates, plugin metadata, and scripts/validate_repo.py aligned. Each skill folder must contain: - SKILL.md — main skill file (required) Optional: additional templates,…

Deletes or force-pushes
Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

serejaris/personal-corp-osword for word, first seen Aug 6, 2026

Other versions1 project uses a version of this.
Word for word · 1
serejaris/personal-corp-os★ 243100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository31 other files it gives its agents.
- art-directorSkill
- audit-agent-rulesSkill
- avatarSkill
- benchmarkSkill
- cc-analyticsSkill
- ceo-councilSkill
- claude-md-writerSkill
- claude-sessions-syncSkill
- corp-doctorSkill
- corp-newSkill
- dailySkill
- fable-ruki-agentySkill
- gh-issuesSkill
- grill-meSkill
- harnessSkill
- html-draftSkill
- ideaSkill
- it-ram-doctorSkill
- make-3dSkill
- make-landingSkill
- managerSkill
- meeting-copilotSkill
- readme-generatorSkill
- retroSkill
- safe-public-releaseSkill
- sdlc-milestonesSkill
- tg-bot-opsSkill
- to-issuesSkill
- to-prdSkill
- weekly-planningSkill
- weekly-retroSkill

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Distinctive:
Never delete skills directories without explicit confirmation
line 17
Distinctive:
Never push to main without running through release checklist
line 18
Very specific:
Never modify SKILL.md frontmatter (name, description) without updating both READMEs
line 19
Distinctive:
Never create GitHub issues/labels in this public repo with private data
line 20
Distinctive:
Update READMEs (only if skills list changed)
line 51
Very specific:
Run a clean Codex install smoke: tmp_home=$(mktemp -d).
line 55

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

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

Files

AGENTS.md

personal-corp-os

Collection of Claude Code customizations: skills, statusline, hooks.

Critical Rules

ALWAYS update BOTH READMEs when releasing:

README.md (English) and README.ru.md (Russian)
Adding/removing skills → update skills list in both READMEs
Adding/removing any component → update corresponding section in both READMEs
Release without README updates = incomplete release
Public repo hygiene changes must keep SECURITY.md, CODE_OF_CONDUCT.md, issue templates, plugin metadata, and scripts/validate_repo.py aligned.

Never

Never delete skills directories without explicit confirmation
Never push to main without running through release checklist
Never modify SKILL.md frontmatter (name, description) without updating both READMEs
Never create GitHub issues/labels in this public repo with private data

Structure

Path	Purpose
`skills/`	Reusable skill templates
`archive/skills/`	Historical skills kept for reference; not active plugin skills
`statusline/`	Custom statusline scripts
`hooks/`	Pre/post command hooks

Skill Structure

Each skill folder must contain:

SKILL.md — main skill file (required)

Optional: additional templates, configs in the same folder.

Versioning

Change	Version	Example
New skill/component	MINOR	1.5.0 → 1.6.0
Update existing skill	PATCH	1.5.0 → 1.5.1
Bug fix, docs	PATCH	1.5.0 → 1.5.1

READMEs update only when skills list changes (add/remove).

Release Checklist

Update CHANGELOG.md
Update READMEs (only if skills list changed)
Run python3 scripts/validate_repo.py
Run claude plugin validate .claude-plugin/marketplace.json
Run claude plugin tag --dry-run --force .
Run a clean Codex install smoke: tmp_home=$(mktemp -d); HOME="$tmp_home" codex plugin marketplace add .; HOME="$tmp_home" codex plugin add personal-corp-os@personal-corp-os; rm -rf "$tmp_home"
Run git diff --check
Commit: docs: update changelog for vX.Y.Z
Tag: git tag -a vX.Y.Z -m "Release vX.Y.Z"
Push: git push && git push --tags
GitHub release via gh release create

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.

Check your setup, free