tninja/ai-code-interface.el

0

/ 100

Documentation59
Engineering54
Health100
Emacs Lisp240Apache-2.01d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Unified Emacs interface supporting OpenAI Codex, Antigravity CLI, Claude Code, GitHub Copilot CLI, Opencode, and more

Documentation

59

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt40

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

54

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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/CD14pt57

CI is configured (.github/workflows/unit-tests.yml).

Reproducibility6pt70

Lockfile present (examples/leetcode/typescript/package-lock.json). Installs are reproducible.

Tests18pt80

Test files detected (examples/battleship/test_fleet.py).

Project health

100

Dependency manifest6pt100

Dependency manifest found (examples/leetcode/typescript/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)
  • 27
    Forks
  • 41
    Releaseslatest 4mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 240
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 13h
    Median PR merge time
  • 11
    Open issues
Repository files64 root entries
  • .github
    Good: CI is configured (.github/workflows/unit-tests.yml).
  • docs
  • etc
  • examples
    Good: Test files detected (examples/battleship/test_fleet.py).
    Good: Lockfile present (examples/leetcode/typescript/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (examples/leetcode/typescript/package.json).
  • prompt
  • snippets
  • test
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • ai-code-agent-shell.el
  • ai-code-agile.el
  • ai-code-ai.el
  • ai-code-aider-cli.el
  • ai-code-antigravity-cli.el
  • ai-code-autoloads.el
  • ai-code-backends-infra-eat.el
  • ai-code-backends-infra-etc.el
  • ai-code-backends-infra-ghostel.el
  • ai-code-backends-infra-vterm.el
  • ai-code-backends-infra.el
  • ai-code-backends.el
  • ai-code-behaviors.el
  • ai-code-change.el
  • ai-code-claude-code.el
  • ai-code-codebuddy-cli.el
  • ai-code-codex-cli.el
  • ai-code-cursor-cli.el
  • ai-code-discussion.el
  • ai-code-doc.el
  • ai-code-eca.el
  • ai-code-file.el
  • ai-code-gemini-cli.el
  • ai-code-git.el
  • ai-code-github-copilot-cli.el
  • ai-code-github.el
  • ai-code-gptel-agent.el
  • ai-code-grok-cli.el
  • ai-code-harness.el
  • ai-code-input.el
  • ai-code-interface.png
  • ai-code-kilo.el
  • ai-code-kiro-cli.el
  • ai-code-mcp-agent.el
  • ai-code-mcp-common.el
  • ai-code-mcp-debug-tools.el
  • ai-code-mcp-http-server.el
  • ai-code-mcp-server.el
  • ai-code-notifications.el
  • ai-code-onboarding.el
  • ai-code-opencode.el
  • ai-code-prompt-mode.el
  • ai-code-session-link.el
  • ai-code-session.el
  • ai-code-task.el
  • ai-code-utils.el
  • ai-code.el
  • clickable_link_ai_session.png
  • emacs_mcp_tool_diagnosis.png
  • emacs_mcp_tools.png
  • HISTORY.org
  • icon.png
  • LICENSE
    Good: Licensed under Apache-2.0.
  • README.org
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • transient_menu.png