test

Automate test generation and issue logging across unit, integration, and end-to-end tests.

12|1|Updated Aug 29, 2025
One-click install
npx skills add https://github.com/Pageloom/weft-id --skill test-pageloom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/Pageloom/weft-id/tree/main/.claude/skills/test
Command: npx skills add https://github.com/Pageloom/weft-id --skill test-pageloom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps developers ensure software quality by guiding test creation, locating bugs, and improving coverage across projects.

Core Features & Use Cases

  • Reads backlog and issue archives to inform testing priorities.
  • Writes tests, logs issues, and documents test results to improve traceability.
  • Can commit changes after user confirmation, enabling safe collaboration.

Quick Start

Start a test-writing session against the current codebase to identify gaps and draft tests.

Frequently Asked Questions about test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate test generation to improve software quality?

Automating test generation improves software quality by reading your codebase and backlog archives to draft unit, integration, and end-to-end tests that target coverage gaps. It analyzes existing test frameworks like pytest to guide test creation and log newly discovered issues.

How does issue logging work during automated test planning?

Issue logging during automated test planning works by documenting test results and writing discovered bugs into archives like ISSUES_ARCHIVE.md. This process improves traceability by linking test failures directly to backlog priorities and recording them for future resolution.

Can I use pytest with a tool that reads BACKLOG_ARCHIVE.md for test coverage?

Yes, you can use pytest with a tool that reads BACKLOG_ARCHIVE.md. The system requires access to your codebase and existing test frameworks like pytest to inform testing priorities and draft tests that improve your overall coverage.

What is the best way to prioritize test creation for existing code?

The best way to prioritize test creation for existing code is to analyze backlog and issue archives to identify critical gaps. By reading files like BACKLOG_ARCHIVE.md, the system drafts tests targeting high-priority areas and logs new issues to improve traceability.

Do I need to manually commit test changes after automated test generation?

You do not need to manually commit test changes immediately, as the system logs issues and writes tests first. After review and user confirmation, it can commit the changes to your codebase, enabling safe collaboration and traceability.