agentleFS
RobThePCGuyRobThePCGuy/Claude-Patent-Creator/skills/testing-assistant/SKILL.md

testing-assistant

Skill206 starsChanged 8 months agoMITView on GitHub

Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    FOR CLAUDE: Test scripts in scripts/ directory.

    line 10
  2. Distinctive:

    Run from project root

    line 12
  3. Distinctive:

    Only run diagnostics if tests fail

    line 14
  4. Distinctive:

    Test MCP tools through Claude Code interface.

    line 54
  5. Distinctive:

    Test after every change

    line 146
  6. Distinctive:

    Test pyramid (more unit, fewer E2E)

    line 148

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Testing Assistant Skill

Expert system for testing and validating the Claude Patent Creator.

FOR CLAUDE: Test scripts in scripts/ directory.

  • Go directly to running appropriate test
  • Run from project root
  • Tests require active venv
  • Only run diagnostics if tests fail

When to Use

Running test suites, validating new features, testing after changes, debugging failures, creating tests, setting up CI/CD, performance testing, E2E validation, regression testing.

Testing Pyramid

         /\
        /  \       E2E (Manual + Automated)
       /----\
      / API  \     Integration Tests
     /--------\
    /  Unit   \    Unit Tests
   /----------\

Strategy: More unit tests (fast, isolated), fewer integration (moderate), minimal E2E (slow).

Test Suite Overview

scripts/
+-- test_install.py          # Complete installation validation
+-- test_gpu.py              # GPU detection and CUDA
+-- test_bigquery.py         # BigQuery connection
+-- test_analyzers.py        # Claims, spec, formalities
+-- test_embedding_speed.py  # Performance benchmarks
+-- test_checkpoint.py       # Index checkpoint system

Quick Test:

python scripts/test_install.py

Manual Testing via Claude

Test MCP tools through Claude Code interface.

Quick Test Examples

1. MPEP Search: "Search MPEP for claim definiteness requirements"
2. Patent Search: "Search for patents about neural networks filed in 2024"
3. Claims Review: "Review these claims: [paste test claims]"
4. Full Review: "/full-review" (with test application)
5. Diagrams: "Create a flowchart for this process: [describe]"

Validation Checklist

[OK] MPEP search returns relevant results
[OK] BigQuery search finds patents
[OK] Claims analyzer identifies issues
[OK] Specification analyzer checks support
[OK] Formalities checker validates format
[OK] Diagrams generate successfully
[OK] Full review workflow completes
[OK] All MCP tools accessible
[OK] Error messages clear and helpful
[OK] Performance acceptable (<2s most ops)

Creating New Tests

Quick Start

# Unit test template
def test_basic_functionality():
    from mcp_server.your_module import YourClass
    instance = YourClass()
    result = instance.method("test input")
    assert result is not None
    print("[OK] test_basic_functionality passed")

Test Categories:

  1. Basic functionality
  2. Edge cases
  3. Performance
  4. Error handling

Performance Testing

Quick Benchmark

from mcp_server.mpep_search import MPEPIndex
import time

index = MPEPIndex()
index.build_index()
index.search("test", top_k=5)  # Warm up

start = time.time()
result = index.search("claim definiteness", top_k=5)
duration = time.time() - start
print(f"Search took: {duration:.3f}s")

Performance Thresholds

OperationThresholdNotes
MPEP search (first)<3sModel loading
MPEP search (subsequent)<500msCached models
BigQuery search<2sNetwork dependent
Claims analysis<3s20 claims
Spec analysis<10s10 pages
Diagram generation<1sSVG output

Troubleshooting Test Failures

ProblemSolution
Import errorsActivate venv, pip install -r requirements.txt
GPU tests failCheck nvidia-smi, reinstall PyTorch, or skip
BigQuery failsRe-auth: gcloud auth application-default login
Index not foundRebuild: patent-creator rebuild-index
Too slowCheck GPU usage, first run slower, check system load

Best Practices

  1. Test after every change
  2. Automated testing
  3. Test pyramid (more unit, fewer E2E)
  4. Fast tests (<5 min suite)
  5. Isolated tests (no dependencies)
  6. Clear assertions
  7. Document tests
  8. Version control tests
  9. Regular execution (weekly)
  10. Monitor performance

Quick Reference

Run All Tests

python scripts/test_install.py
python scripts/test_gpu.py
python scripts/test_bigquery.py
python scripts/test_analyzers.py
python scripts/test_embedding_speed.py

Regression Test

python scripts/test_install.py || exit 1
python scripts/test_bigquery.py || exit 1
python scripts/test_analyzers.py || exit 1
echo "[OK] All regression tests passed!"

Manual Checklist

□ Ask Claude to search MPEP
□ Ask Claude to search patents
□ Ask Claude to review claims
□ Run /full-review command
□ Generate a diagram
□ Verify all tools work
□ Check performance (<2s)

Download now (ZIP)

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.