artifacts/bundle/skills/engineering-team/report/SKILL.md
# Smart Test Reporting Generate test reports that plug into the user's existing workflow. Zero new tools. ## Steps ### 1. Run Tests (If Not Already Run) Check if recent test results exist: ```bash ls -la test-results/ playwright-report/ 2>/dev/null ``` If no recent results, run tests: ```bash npx playwright test --reporter=json,html,list 2>&1 | tee test-output.log ``` ### 2. Parse Results Read the JSON report: ```bash npx playwright test --reporter=json 2> /dev/null ``` Extract: - To
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/engineering-team/reportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate test reports that plug into the user's existing workflow. Zero new tools.
Check if recent test results exist:
ls -la test-results/ playwright-report/ 2>/dev/null
If no recent results, run tests:
npx playwright test --reporter=json,html,list 2>&1 | tee test-output.log
Read the JSON report:
npx playwright test --reporter=json 2> /dev/null
Extract:
Check what's configured and route automatically:
| Check | If found | Action |
| --------------------------- | ------------------- | -------------------------------------- |
| TESTRAIL_URL env var | TestRail configured | Push results via /pw:testrail push |
| SLACK_WEBHOOK_URL env var | Slack configured | Post summary to Slack |
| .github/workflows/ | GitHub Actions | Results go to PR comment via artifacts |
| playwright-report/ | HTML reporter | Open or serve the report |
| None of the above | Default | Generate markdown report |
# Test Results — {{date}}
## Summary
- ✅ Passed: {{passed}}
- ❌ Failed: {{failed}}
- ⏭️ Skipped: {{skipped}}
- 🔄 Flaky: {{flaky}}
- ⏱️ Duration: {{duration}}
## Failed Tests
| Test | Error | File |
| -------- | --------- | ----------------- |
| {{name}} | {{error}} | {{file}}:{{line}} |
## Flaky Tests
| Test | Retries | File |
| -------- | ----------- | -------- |
| {{name}} | {{retries}} | {{file}} |
## By Project
| Browser | Passed | Failed | Duration |
| -------- | ------ | ------ | -------- |
| Chromium | X | Y | Zs |
| Firefox | X | Y | Zs |
| WebKit | X | Y | Zs |
Save to test-reports/{{date}}-report.md.
curl -X POST "$SLACK_WEBHOOK_URL" \
-H 'Content-Type: application/json' \
-d '{
"text": "🧪 Test Results: ✅ {{passed}} | ❌ {{failed}} | ⏱️ {{duration}}\n{{failed_details}}"
}'
Invoke /pw:testrail push with the JSON results.
npx playwright show-report
Or if in CI:
echo "HTML report available at: playwright-report/index.html"
If previous reports exist in test-reports/:
Creator: Engineering Team License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:engineering-teamOriginal Path:engineering-team/playwright-pro/skills/report
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski