dyoshikawa/rulesync

0

/ 100

Documentation80
Engineering83
Health100
TypeScript1,185MIT1d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

A Utility CLI for AI Coding Agents

Documentation

80

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

83

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt85

CI is configured (.github/workflows/ci-failure-reminder.yml).

Tests18pt100

Test files detected (scripts/pr-continuation.test.ts).

Linting and formatting5pt100

Linter or formatter configured (devDependency in package.json).

Reproducibility6pt100

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 132
    Forks
  • 253
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,185
    Watchers

Responsiveness

  • 2d 14h
    Median issue response
  • <1h
    Median PR merge time
  • 44
    Open issues
Repository files41 root entries
  • .claude
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/ci-failure-reminder.yml).
    Good: Dependabot covers 3 ecosystems (npm, github-actions, docker). Dependencies stay current.
  • .opencode
  • .rulesync
    Good: Licensed under MIT.
  • .vscode
  • .zed
  • docs
  • images
  • patches
  • scripts
    Good: Test files detected (scripts/pr-continuation.test.ts).
  • skills
  • src
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gtrconfig
  • .lintstagedrc.js
  • .npmrc
  • .oxfmtrc.json
  • .oxlintrc.json
  • .rulesyncignore
  • .secretlintrc.json
  • .trivyignore
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • cspell.json
  • GOVERNANCE.md
  • install.sh
  • knip.ts
  • LICENSE
  • mise.toml
  • opencode.json
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rulesync.jsonc
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.json
  • vitest.config.ts
  • vitest.e2e.config.ts