agentleFS
Sign inStart free
AlaSQLAlaSQL/alasql/.github/copilot-instructions.md

alasql

Copilot instructions7.3k starsChanged 21 days agoMITView on GitHub

AlaSQL is an open source SQL database for JavaScript with a focus on query speed and data source flexibility for both relational data and schemaless data. It works in web browsers, Node.js, and mobile apps.

We split this copilot-instructions.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    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
  1. Distinctive:

    Understand the issue thoroughly: - Read related test cases and existing code

    line 9
  2. Very specific:

    Verify test fails: - Run yarn test to confirm the test catches the issue

    line 11
  3. Very specific:

    If you modify the grammar in src/alasqlgrammar.jison, run yarn jison && yarn test to regenerate the parser and verify

    line 13
  4. Distinctive:

    Reconsider elegance: - Make sure to assess the solution and reconsider if this can be more elegant or efficient

    line 14
  5. Very specific:

    Format code: - Run yarn format before committing

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
copilot-instructions.md

GitHub Copilot Instructions for AlaSQL

About This Project

AlaSQL is an open source SQL database for JavaScript with a focus on query speed and data source flexibility for both relational data and schemaless data. It works in web browsers, Node.js, and mobile apps.

When Implementing Features

  1. Understand the issue thoroughly - Read related test cases and existing code
  2. Write a test first - Copy test/test000.js into a new file called test/test###.js where where ### is the id of the issue we are trying to solve.
  3. Verify test fails - Run yarn test to confirm the test catches the issue
  4. Implement the fix - Modify appropriate file(s) in src/
  • If you modify the grammar in src/alasqlgrammar.jison, run yarn jison && yarn test to regenerate the parser and verify
  1. Reconsider elegance - Make sure to assess the solution and reconsider if this can be more elegant or efficient
  2. Format code - Run yarn format before committing

Commands

# Install dependencies
yarn

# Generate grammar (if needed)
yarn jison

# Run tests
yarn test

# Format code
yarn format

Files to Avoid Modifying

  • dist/ - Generated files, will be overwritten on build
  • src/alasqlparser.js - Generated from Jison grammar (modify the .jison file instead)
  • .min.js files - Generated during build

Plesae note

  • Alasql is meant to return undefined instead of null (unline regular SQL engines)

Resources

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about AlaSQL/alasql

The biggest 5 of 55 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 55

Talked about on GitHub, Hacker News and Stack Overflow (55 times).

On GitHub · 50

45 more on GitHub

On Stack Overflow · 2

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 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.

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