colab-app

Imported from priyanshujain/colab-app (AGENTS.md). Install upstream with npx skills add priyanshujain/colab-app. Copyright stays with the author.

Project Guidelines

• Do not call the task done until it is fully complete and tested.
• Never call a task done without manually testing it end to end with the real installed binary against real services. Unit tests and dry runs are not enough. If a step needs the user (QR scan, phone, login), say so explicitly and do not claim it works.
• Always write tests for new features and bug fixes.
• Do not dismiss bug as a pre-existing" issue even if it was present before your change. It does not matter, it's still your responsibility to fix it. When you see a bug, fix it. Don't ignore it.

Coding Guidelines

• Keep code simple and easy to read.
• Write code in the minimum number of lines.
• No comments unless they are extremely necessary, the 0.1% case where the code cannot explain itself.

Testing Guidelines

• Test quality ranks above code quality. Tests are the gatekeepers.
• Never compromise on test quality, even if it delays a release by a week.
• Think hard before writing any test. Every test must be the highest quality you can write.
• Bad tests are never accepted: no shallow unit tests, no unrealistic scenarios, no toy examples. Test realistic inputs and real behaviour.

Destructive Actions

• NEVER delete databases, config files, or user data. If a schema changes, rename/migrate in place.
• Always prefer non-destructive alternatives (ALTER TABLE RENAME, mv, cp) over delete-and-recreate.
• Ask before removing any file that contains user data.

Git Branch Rules

• Never create a branch unless explicitly asked. Keep working on the current branch.
• No slashes in branch names (e.g., use fix-something not fix/something).

Git Commit Rules

• never use commit prefix like feat: write a small plain text smallcase commit messages
• Never use git add . or git add -A. Always stage specific files by name.
• Don't batch multiple unrelated changes into one commit.

Pull Request Rules

• PR descriptions are plain text. No markdown, no headings, no bullets, no bold, no code blocks, no emoji, no tables.
• A few lines, Super casual that's it. Don't write an essay.