Repository navigation
Conversation
Move the line-capture and line-analyze commands to .agents/skills, with their scripts next to them, and link .claude/skills to .agents/skills so Claude Code finds them. The capture launcher now runs a dependency preflight first and works on macOS, Linux and Windows (Git Bash). The CDP recorder releases every page-like target so extension windows no longer open frozen. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Writes the numbered test plan (test/<feature>/PLAN.md) for a bridge feature before any capture or code: lettered sections, stable step IDs, before/capture/after phases and a Result column, plus labeled sample media when the feature needs files. check-plan.py validates the layout and make-samples.py generates the samples. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
line-test-planskill, which writes a numbered test plan for a bridge feature before any capture or code. Depends on #288: review that one first, and only the last commit here is new.🇬🇧 More details
Summary
line-test-planwritestest/<feature>/PLAN.mdbefore any capture or code. The plan lists what to do in LINE, Beeper and the Chrome Extension, numbered so that every screenshot, request and result can point at a step.Why
Part 2 of 5 of the stack that brings the LINE skills into this repo, as asked on #280. A numbered plan makes captures and PR evidence easy to check: each finding names the step it came from.
Changes
New folder
.agents/skills/line-test-plan/:SKILL.md: the workflow. It asks about test chats, devices and a second account first. The plan has lettered sections, stable step IDs (A1,B5), a phase per step (before,capture,after), a Result column, a coverage table and known gaps.TEMPLATE.md: the plan layout.scripts/check-plan.py: checks a plan against the layout.scripts/make-samples.py: makes labeled sample media for media features, with a size ladder.scripts/line-test-plan-preflight.sh: checks Python, Pillow and ffmpeg with its encoders.test/is already in.gitignore, so plans and samples stay local.How it was tested
line-test-planreads that guide when it plans a media feature.OK.bash -nand a Python syntax check on the scripts, andpre-commit runon every changed file: passed.Not tested (and why)
Related
🤖 Generated with Claude Code using clins:create-pr