by he-yufeng
Auto-generate AI assistant rules (CLAUDE.md, .cursorrules, copilot-instructions) from codebase analysis
# Add to your Claude Code skills
git clone https://github.com/he-yufeng/RuleForgeLast scanned: 6/1/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-06-01T09:27:21.624Z",
"npmAuditRan": true,
"pipAuditRan": true
}RuleForge is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by he-yufeng. Auto-generate AI assistant rules (CLAUDE.md, .cursorrules, copilot-instructions) from codebase analysis. It has 126 GitHub stars.
Yes. RuleForge passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/he-yufeng/RuleForge" and add it to your Claude Code skills directory (see the Installation section above).
RuleForge is primarily written in Python. It is open-source under he-yufeng on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh RuleForge against similar tools.
No comments yet. Be the first to share your thoughts!
Auto-generate AI coding assistant rules from your codebase.
RuleForge scans your project — languages, frameworks, linters, test setup, CI config — and generates ready-to-use rule files for Claude Code (CLAUDE.md), Cursor (.cursorrules), and GitHub Copilot (.github/copilot-instructions.md).
Stop writing these files by hand. Let your codebase speak for itself.
Every AI coding assistant works better with project-specific context. But most developers either:
RuleForge generates accurate, stack-aware rules in seconds by actually reading your project config.
| Category | Examples |
|---|---|
| Languages | Python, TypeScript, JavaScript, Go, Rust, Java, C++, and 20+ more |
| Frameworks | FastAPI, Flask, Django, React, Next.js, Vue, Svelte, Express, Gin, Axum... |
| Package Managers | pip, poetry, hatch, pnpm, yarn, bun, npm, cargo |
| Linters & Formatters | ruff, black, eslint, prettier, biome, clippy, go fmt |
| Test Frameworks | pytest, unittest, vitest, jest, mocha |
| CI Systems | GitHub Actions, GitLab CI, CircleCI, Jenkins |
| Other | Docker, Makefile, monorepo structure, entry points, .gitignore patterns |
Language counts respect .gitignore, so generated bundles and local artifacts do not skew the detected stack.
pip install ruleforge
# Scan your project to see what's detected
ruleforge scan .
# Generate all rule files (CLAUDE.md, .cursorrules, copilot-instructions)
ruleforge generate .
# Generate only CLAUDE.md
ruleforge generate . -f claude
# Preview without writing anything
ruleforge preview .
# Audit existing assistant rules for missing guidance
ruleforge audit .
# Fail CI if the rules are too thin
ruleforge audit . --min-score 80
# Overwrite existing files
ruleforge generate . --overwrite
# Output to a different directory
ruleforge generate . -o /tmp/rules
Running ruleforge generate on a FastAPI project produces a CLAUDE.md like:
# my-api
This is a Python project.
Key frameworks: FastAPI, Pydantic, SQLAlchemy.
## Project Structure
Source directories: `src/`, `tests/`
Entry points: `main.py`
Package manager: poetry
## Coding Conventions
- Linter: ruff
- Formatter: ruff
- Testing: pytest
- Python: >=3.11
- CI: GitHub Actions
## Guidelines
- Use type hints for function signatures.
- Run `ruff check` and `ruff format` before committing.
- Write tests with pytest. Put test files in the `tests/` directory.
- Use Pydantic models for request/response schemas.
- The project uses Docker. Keep Dockerfile up to date with dependencies.
## Do NOT
- Do not modify generated files or lock files manually.
- Do not add dependencies without mentioning it.
- Do not change the project structure without asking first.
- Do not skip CI checks or disable linting rules.
- Do not commit files matching gitignore patterns.
| Format | File | Used By |
|---|---|---|
claude |
CLAUDE.md |
Claude Code, Claude Desktop |
cursor |
.cursorrules |
Cursor IDE |
copilot |
.github/copilot-instructions.md |
GitHub Copilot |
RuleForge can also check rule files you already wrote. It looks for the parts that usually make AI coding agents useful in a real repository:
.env handlingruleforge audit .
ruleforge audit . --format json
ruleforge audit . --min-score 80
This is useful for CI or for checking whether a hand-written AGENTS.md, CLAUDE.md, .cursorrules, or Copilot instructions file is specific enough to trust.
from ruleforge import analyze_project, generate_rules
from ruleforge.generator import write_rules
# Analyze
profile = analyze_project("./my-project")
print(profile.languages) # {'Python': 42, 'TypeScript': 15}
print(profile.frameworks) # ['FastAPI', 'React']
# Generate
rules = generate_rules(profile, formats=["claude", "cursor"])
for rule in rules:
print(rule.filename, len(rule.content))
# Write to disk
write_rules(rules, "./my-project")
Contributions welcome! Especially for:
analyzer.py)generator.py)git clone https://github.com/he-yufeng/RuleForge.git
cd RuleForge
pip install -e ".[dev]"
pytest
MIT