Skip to content

Add official agent-qa testing skills - #137

Open
pranshuchittora wants to merge 3 commits into
nextlevelbuilder:mainfrom
pranshuchittora:add-agent-qa-skills
Open

pranshuchittora wants to merge 3 commits into
nextlevelbuilder:mainfrom
pranshuchittora:add-agent-qa-skills

Conversation

@pranshuchittora

@pranshuchittora pranshuchittora commented Oct 25, 2026 •

Copy link
Copy Markdown

Add the four existing official agent-qa skills to the curated testing catalog: authoring, debug/fix, result triage, and knowledge inspection. agent-qa by vostride brings natural-language QA for web, Android, and iOS together with advanced memidex memory and self-improvement.

This follows the manual curation workflow in scripts/README.md: add records to build-seed-data.mjs, then regenerate seed-data.json. All 5,113 existing records remain unchanged; the catalog grows to 5,117. Each entry links its official skill directory and includes an individual install command. New install/rating counters are zero; 912 GitHub stars were observed on 2026-10-31; the source records now include the capture date. Skills are not independently versioned, so the optional version field is omitted.

The entries disclose Node.js 24+, runtime/provider setup, possible provider/device costs, and the FSL-1.1-ALv2 source license. These are catalog summaries of the existing skills, not changes to the skills or product. I am affiliated with vostride.

Original validation (2026-10-25) on Node.js 22.22.2 / pnpm 10.22.0:

  • All CI commands pass: workspace typecheck, CLI build and version/help/release-help checks, 2,634 tests (3 skipped), and web build.
  • Native generation is idempotent, all existing records are preserved, and git diff --check passes.
  • assert-seed-identity.mjs reports the same 48 duplicate source identities and 4 noncanonical slugs on unchanged upstream 95b51df and this branch; the four new entries introduce no additional errors.
  • The guide's pnpm lint and root pnpm tsc --noEmit commands are unavailable in the current root package. The actual workspace pnpm typecheck succeeds.

Validation covers this catalog contribution. It does not claim a live agent-qa application run, Claude Code session, or deployment to SkillX.

Source: https://github.com/vostride/agent-qa/tree/main/skills

Review update (2026-10-31): retained the shared product overview only in the authoring entry and refreshed the dated star snapshot. JavaScript syntax, native generation, idempotency, unchanged-record comparison, and whitespace checks pass; all 5,113 unrelated entries are unchanged.

Follow-up to the 2026-10-31 re-review: the star snapshot date now appears in the rendered content of all four agent-qa entries. Regenerated seed-data.json using the native builder; all 5,113 other records and every non-content field are unchanged. git diff --check passes. The first-time-contributor workflow approval remains a maintainer action.

@clark-cant clark-cant left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary: Adds four curated catalog entries for vostride's agent-qa skill family (authoring, debug/fix, result triage, knowledge) to scripts/build-seed-data.mjs and regenerates scripts/seed-data.json (+128/−0 across 2 files). No product code is touched.

Risk level: Low

Mandatory gates

  • Duplicate / prior implementation: clear — no existing vostride/* or agent-qa slug among the 5,113 records, and no other PR or issue covers this family.
  • Project standards: docs found — scripts/README.md documents the curated-add workflow, the skill schema, the category enum (testing is valid) and the npx skills add … install-command convention used by every existing record.
  • Strategic necessity: clear value — adds breadth to the testing category (1,113 of 5,113 records), with vendor affiliation disclosed in the description.

Verification performed

  • All four source_url directories exist on vostride/agent-qa (skills/agent-qa-{authoring,debug-fix,result-triage,knowledge}), each with a SKILL.md whose name matches the --skill selector.
  • LICENSE.md in that repo is the Functional Source License 1.1, ALv2 Future License, matching the disclosed "FSL-1.1-ALv2". GitHub reports the repo licence as "Other"/NOASSERTION only because FSL is non-standard, so the claim in the entry is accurate — and the licence file does ship, which matters for #145.
  • build-seed-data.mjs skips slugs that already exist, so a re-run adds 0 rows; the seed-data.json diff is consistent with a real regeneration.
  • github_stars: 893 is in line with the repo (908 at review time).

Findings

  • Critical: none
  • Important: none
  • Suggestion: the same promotional paragraph ("agent-qa by vostride runs natural-language QA … self-improvement across runs.") is repeated verbatim in all four content fields. content is what search results and detail pages render, so keeping it once (or trimming it to a clause per entry) would reduce noise.
  • Suggestion: github_stars is a 2026-10-25 snapshot; worth refreshing before merge or noting the capture date, since curated rows are not refreshed by the store.

Not a code issue, but blocking merge: no workflow ran on this PR (statusCheckRollup is empty, mergeStateStatus is UNSTABLE), which is the usual first-time-contributor workflow-approval gate. A maintainer needs to approve the runs before this can go green.

Verdict: Comment — minor suggestions only, safe to merge once CI is approved.

Posted by /github-maintain (ck:review-pr) at 2026-10-29T16:06:36Z

@pranshuchittora

Copy link
Copy Markdown
Author

Addressed both suggestions in fe9770a: the shared product overview now appears only in the authoring entry, and all four star counts use the 2026-10-31 snapshot (912), with the capture date recorded beside the curated entries. Native generation is idempotent; exactly the four agent-qa records change and the other 5,113 entries are unchanged. Syntax and whitespace checks pass.

@clark-cant clark-cant left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-review at fe9770a (second commit, +15/-14 over the same two files). Both suggestions from the 2026-10-29 review are addressed, and nothing new was introduced.

What changed and what I verified

  • Repeated product overview removed. The "agent-qa by vostride runs natural-language QA ..." paragraph now appears in exactly one content field (vostride-agent-qa-authoring); the debug-fix, result-triage and knowledge entries each keep only their own summary plus the requirements/licence paragraph.
  • Star snapshot refreshed and dated. All four entries are github_stars: 912, matching vostride/agent-qa at review time (912 stargazers), with a comment above the first entry recording the 2026-10-31 capture date.
  • Regeneration is genuine, not a hand edit. scripts/seed-data.json at the head parses cleanly and holds 5,117 records with 4 vostride-agent-qa-* entries, category: testing, zero duplicate slugs, and only those four records touched — the other 5,113 are unchanged, exactly as the PR body claims (+65/-0 in build-seed-data.mjs, +64/-0 net in seed-data.json).
  • Source provenance still holds. The four source_url skill directories exist on vostride/agent-qa, and the repo licence remains FSL-1.1-ALv2, which is what the entries disclose.

Remaining (suggestion, not blocking)

  • The capture date lives only as a code comment in build-seed-data.mjs. seed-data.json — the artifact the store actually renders — carries no date, so a future reader of the catalog cannot tell how old the 912 figure is. If the freshness matters, put the date in the entry content or accept the source comment as the record.

Merge state (unchanged, not a code problem)

  • statusCheckRollup is still empty and the checks API reports state: pending, total_count: 0 for fe9770a — no workflow has ever executed on this branch. This is the first-time-contributor approval gate, so no gate can turn green until a maintainer approves the workflow runs.
  • reviewDecision is empty; mergeStateStatus is UNSTABLE; no approving review exists.

Verdict: Comment — both prior suggestions resolved, no critical or important findings. Safe to merge once a maintainer approves the workflow runs.

Posted by /ck:review-pr at 2026-10-31T10:05:00Z

Signed-off-by: vostride <pranshuchittora@users.noreply.github.com>

@clark-cant clark-cant left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-review at d688022 (third commit: +4/-4 in scripts/build-seed-data.mjs, +4/-4 in scripts/seed-data.json). The one remaining suggestion is resolved and nothing else moved.

What changed and what I verified

  • The date is now in the rendered content. All four agent-qa content strings end their requirements paragraph with GitHub stars checked on 2026-10-31. — exactly 4 occurrences in the generator and 4 in the artifact, and no other text differs.
  • Parity with main is exact. Parsed scripts/seed-data.json at the head: 5,117 records versus 5,113 on main — the 4 vostride-agent-qa-* records added, 0 modified, 0 removed. All four remain category: testing with github_stars: 912.
  • This is a real regeneration, not a hand edit. Each of the four JSON content values appears as an exact JSON literal in build-seed-data.mjs at the head, so the generator and the artifact agree byte for byte.
  • Nothing else in the PR moved: same two files, same four install commands, same FSL-1.1-ALv2 disclosure, git diff --check clean as claimed.

Nit (cosmetic, not worth a commit)

The new sentence carries the date but not the number — the count lives in the separate github_stars: 912 field, so "GitHub stars checked on 2026-10-31." reads slightly oddly on its own. "912 GitHub stars as of 2026-10-31" would be self-contained. No action needed.

Merge state (unchanged, and not something the author can fix)

  • check-runs for d688022 returns total_count: 0 — no workflow has ever executed on this branch. That is the first-time-contributor workflow-approval gate.
  • reviewDecision is empty; mergeStateStatus is UNSTABLE; no approving review exists.

Verdict: Comment — the last suggestion is addressed, no critical or important findings, and no further re-review is needed from this side. Safe to merge once a maintainer approves the workflow runs.

Posted by /ck:review-pr at 2026-10-31T16:05:54Z

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants