a-saven

@a-saven source repo

6 skills
0 followers
9 hours ago last updated

▌
QA Run · a-saven
Orchestrate a manual-QA pass (functional or design) on the running app in ANY project — a WEB app in a browser or a NATIVE iOS app in the Simulator. Detects whether the project is a single app or a monorepo, remembers a dev URL and login credentials PER APP, plus an optional read-only DB, asking only for what isn't saved yet (and remembering "declined" so it never re-asks). Then scopes the run to the app(s) being tested and invokes the manual-qa agent. Use when the user asks to "QA this", "verify the app works", "test the flow", "check if X works / looks right in the browser", "test the native app / in the simulator", or invokes /qa-run. Runs in the MAIN thread (it needs to ask the user questions); it sets up context, then delegates the click-through to the manual-qa subagent. Also supports an unattended task mode where a parent injects a per-task URL/port (or Simulator UDID) + worktree and no questions are asked.

0 installs
▌
Ticket · a-saven
Create Linear or Jira tickets that read like a human wrote them — not AI slop. Detects which tracker a project uses (Linear vs Jira) and remembers the team/project mapping per project, asking only once. Handles both bug reports and new-feature handoffs, written for the tester who picks it up — a bug gets reproduction steps + where it lives; a feature gets what it solves, where to find it, the design, and how to test it. Writes a short, scannable ticket (plain language, real paths/flows, concrete test steps, observable acceptance) and enriches it from whatever useful MCPs are connected — renders Figma frames, pulls Sentry error context, reads the originating Slack thread, links the relevant PR — using only what's installed and relevant. Posts recent test results (qa-run, test runs, CI) and long evidence as a comment instead of bloating the description. Use when the user asks to "create a ticket", "file a bug", "open an issue", "make a Linear/Jira ticket", "log this", or invokes /ticket. Runs in the MAIN thread

0 installs
▌
Graphify · a-saven bundle
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

0 installs
▌
Orchestrate · a-saven
Orchestrate non-trivial engineering work by scoping it, decomposing it into a parallel task DAG, delegating each node to the cheapest model tier that can meet its acceptance criteria, and verifying before integration. Use this whenever a task involves more than a single mechanical edit — implementing a feature, a cross-cutting refactor, a bugfix with an unknown root cause, a migration, or anything where you are about to spawn subagents or start editing several files. Also use it when the user says "plan this", "break this down", "delegate", "route this", "use subagents", "orchestrate", or hands over a vague ask like "add auth" that needs pinning down before any code is written. Reads the repo's CLAUDE.md for stack conventions and forwards them into every delegated brief. Written for a top-tier orchestrator model; do not skip it just because the task looks tractable solo — routing is the point.

0 installs
▌
Playwright QA · a-saven
Playwright QA (headless, via Playwright MCP)

0 installs
▌
Worktree Graphs · a-saven
Check, seed, or repair the CodeGraph index and Graphify graph across a repo's git worktrees. Use when a session is running in a worktree and CodeGraph looks absent or wrong, when the user asks whether the graphs are fresh / "check all worktrees", after creating a worktree (Orca, `git worktree add`, or an agent harness), or when a graph answer disagrees with the code actually on disk. Also covers why a Graphify graph goes stale after `git pull` and how to force a refresh.

0 installs

6 published skills