Django TDD
affaan-m/ECC
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
Write or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns.
$ npx skills add baserow/baserow --skill write-backend-unit-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install baserow/baserow write-backend-unit-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-backend-unit-test .claude/skills/write-backend-unit-test && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-backend-unit-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-test into .claude/skills/write-backend-unit-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-backend-unit-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add baserow/baserow --skill write-backend-unit-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install baserow/baserow write-backend-unit-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-backend-unit-test .agents/skills/write-backend-unit-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-backend-unit-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-test into .agents/skills/write-backend-unit-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-backend-unit-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add baserow/baserow --skill write-backend-unit-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install baserow/baserow write-backend-unit-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-backend-unit-test .cursor/skills/write-backend-unit-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-backend-unit-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-test into .cursor/skills/write-backend-unit-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-backend-unit-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/baserow/baserow.git --path .agents/skills/write-backend-unit-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add baserow/baserow --skill write-backend-unit-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install baserow/baserow write-backend-unit-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-backend-unit-test .gemini/skills/write-backend-unit-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-backend-unit-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-test into .gemini/skills/write-backend-unit-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-backend-unit-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install baserow/baserow write-backend-unit-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add baserow/baserow --skill write-backend-unit-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-backend-unit-test .github/skills/write-backend-unit-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-backend-unit-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-test into .github/skills/write-backend-unit-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-backend-unit-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add baserow/baserow --skill write-backend-unit-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install baserow/baserow write-backend-unit-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/baserow/baserow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-backend-unit-test .opencode/skills/write-backend-unit-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-backend-unit-test" agent skill from https://github.com/baserow/baserow/tree/develop/.agents/skills/write-backend-unit-test into .opencode/skills/write-backend-unit-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-backend-unit-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
write-backend-unit-testWrite or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns.
Write Backend Unit Test is an agent skill from baserow/baserow. Write or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering Unit testing and Backend development. It works with pytest, Django and Airtable. The repository describes itself as: Build databases, automations, apps & agents with AI — no code. Open source platform available on cloud and self-hosted. GDPR, HIPAA, SOC 2 compliant. Best Airtable alternative.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 68aec3c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
justFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Write Backend Unit Test loads about 1.8k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 749 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 749 words (~1,750 tokens).
“Use this skill when a task is to add, fix, or extend a backend test in backend/tests, premium/backend/tests, or enterprise/backend/tests.”
SKILL.md and 1 other file in .agents/skills/write-backend-unit-test of baserow/baserow.
Open the folder on GitHubat commit 68aec3c
Write Backend Unit Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Backend Unit Test this skillbaserow/baserow | 6.1k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Django TDDaffaan-m/ECC | 274k | 7 repos | ~5.3k | Automated safety check: Pass | MIT | |
| Dj Pytestdvf/opinionated-django | 109 | — | ~4.3k | Automated safety check: Notes | MIT | |
| Django TDDaffaan-m/ECC | 274k | 3 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Django TDDxu-xiang/everything-claude-code-zh | 2k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Pytestbobmatnyc/claude-mpm | 155 | — | ~8.2k | Automated safety check: Pass | MIT |
affaan-m/ECC
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
dvf/opinionated-django
Set up and write pytest tests for an op-django project — pytest-django configuration, two-sided Celery testing (patched dispatch sites + plain-function task bodies, never eager mode), freezegun for…
affaan-m/ECC
Django 测试策略,包括 pytest-django、TDD 方法、factoryboy、模拟、覆盖率以及测试 Django REST Framework API。
xu-xiang/everything-claude-code-zh
使用 pytest-django 进行 Django 测试的策略、TDD 方法论、factoryboy、Mock 模拟、测试覆盖率以及测试 Django REST Framework API。
bobmatnyc/claude-mpm
pytest - Python's most powerful testing framework with fixtures, parametrization, plugins, and framework integration for FastAPI, Django, Flask
mathiasertl/django-ca
Instructions for running, writing, and maintaining tests in this project
baserow/baserow
Review a Baserow pull request, branch, or diff against its actual base the way the maintainers do.
baserow/baserow
Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…
baserow/baserow
Generate a changelog entry for the current Git branch by inspecting changed files, classifying the domain and type, writing a short public-friendly message, and running just changelog add after the…
baserow/baserow
Investigate backend performance using Django Silk profiling data.
baserow/baserow
Explain, create, update, or use Baserow registries across backend and frontend code, including Instance/Registry patterns, registration points, model-backed type registries, serializer/API…
baserow/baserow
A skill your agent uses when working on code involving Element/Page relationships in the Application Builder (contrib/builder) or AutomationNode/AutomationWorkflow relationships in the Automation…
Categories
Write or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns. Write Backend Unit Test is an agent skill from baserow/baserow. Write or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns.
Write Backend Unit Test fits situations like: tasks that involve Unit testing; tasks that involve Backend development.
Run `npx skills add baserow/baserow --skill write-backend-unit-test -a claude-code`. Or copy the skill folder (.agents/skills/write-backend-unit-test in baserow/baserow) into .claude/skills/write-backend-unit-test in your project. Claude Code loads it when a task matches its description.
Run `npx skills add baserow/baserow --skill write-backend-unit-test -a codex`. Or copy the skill folder (.agents/skills/write-backend-unit-test in baserow/baserow) into .agents/skills/write-backend-unit-test in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add baserow/baserow --skill write-backend-unit-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-backend-unit-test, .gemini/skills/write-backend-unit-test, .github/skills/write-backend-unit-test and .opencode/skills/write-backend-unit-test in your project.
Going by SKILL.md and its folder, Write Backend Unit Test needs the command-line tools its instructions call (just).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Write Backend Unit Test has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Write Backend Unit Test: Django TDD (affaan-m/ECC, 274k stars), Dj Pytest (dvf/opinionated-django, 109 stars), Django TDD (affaan-m/ECC, 274k stars) and Django TDD (xu-xiang/everything-claude-code-zh, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
baserow (a GitHub organization) maintains it in baserow/baserow, which has 6,092 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: baserow/baserow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.