ワンクリックでManusで任意のスキルを実行

$pwd:

pr-ready

Name: Pr Ready
Author: punitarani

// Use when getting an abadge PR merge-ready, checking whether a branch is mergeable, resolving conflicts against main, recovering after a rebase, verifying CI is green, or shepherding a PR through checks and review comments. Triggers on "is this merge-ready", "get this PR green", "rebase onto main", "did I lose commits", "force push", "address the review comments".

Manusで実行

$ git log --oneline --stat

stars:1

forks:0

updated:2026年5月29日 23:31

SKILL.md

readonly

name	pr-ready
description	Use when getting an abadge PR merge-ready, checking whether a branch is mergeable, resolving conflicts against main, recovering after a rebase, verifying CI is green, or shepherding a PR through checks and review comments. Triggers on "is this merge-ready", "get this PR green", "rebase onto main", "did I lose commits", "force push", "address the review comments".

PR Ready

Read the ## Git & PR workflow section in AGENTS.md if PR or CI behavior changed.

Trust These Facts

Required PR checks live in .github/workflows/ci-cd.yml.
Merge-gating jobs: changeset-check, lint, audit, typecheck, test-unit, test-integration, test-web, e2e, build-api, build-cli, build-web, db-validate.
Local equivalents: bun run lint, bun run typecheck, bun run test:cov:unit, bun run test:cov:integration, bun run --cwd apps/web test, bun run test:e2e.
Release-surface paths live in scripts/releases/registry.ts (packages cli, mcp). Touching them requires a changeset in .changeset/, or changeset-check blocks the PR.
Base branch is main. Rebase onto origin/main. The repo merges with merge commits, not squash.
"Merge-ready" means CI is green via gh pr checks, not that the diff looks right.

Use This Workflow

Snapshot before touching history. Record the tip so a bad rebase is recoverable: git rev-parse HEAD (and git reflog is always available). Never start a rebase blind.
Sync and rebase. git fetch origin && git rebase origin/main. Resolve conflicts against origin/main. Rebase in small increments, not one long chain.
Verify nothing was stripped. Compare commit count/subjects against the snapshot. If commits vanished, recover with git reflog + git cherry-pick — do not redo the work from memory.
Run the local gate. bun run lint && bun run typecheck, then the relevant test buckets. Fix failures (including SSR/build breaks — see the SSR-safe-state rule in AGENTS.md Web rules) before pushing.
Changesets. If the diff touches a release surface, add a changeset (bun run changeset) describing the bump.
Push. git push --force-with-lease (never bare --force).
Confirm CI. gh pr checks <pr> — wait for every gating job to pass.
Address review. Resolve Greptile/reviewer comments; keep replies concise; re-run the gate after changes.

Only Report Merge-Ready When

gh pr checks <pr> shows all gating jobs green (not pending, not skipped-by-error).
No commits were lost in rebase (verified against the step-1 snapshot).
Changeset present if a release surface changed.

Until all three hold, report status honestly ("CI still running", "2 checks red") — never "merge-ready".

related-skills.json

同じリポジトリ

abadge-e2e-sweep.md

from "punitarani/abadge"

Use when the user wants to run, resume, monitor, or stop a long-running end-to-end test sweep of the abadge codebase (web, API, CLI, MCP, daemon, crypto, DB, SDK), including phrases like "sweep abadge", "run the e2e audit", "continue the test campaign", "resume the sweep", "what's the sweep finding", "stop the sweep", or any request to methodically test every surface of abadge in a loop with subagents and durable issue tracking.

2026-05-291

abadge-security-audit.md

from "punitarani/abadge"

Use when the user wants to run, resume, monitor, or stop a deep, multi-wave security/compliance audit of the abadge codebase — code review, pen testing, threat modelling, and the full cybersecurity review pipeline. Triggers on phrases like "security audit abadge", "pen test the codebase", "start the security review", "continue the security audit", "what did the audit find", "generate the security report", "stop the audit", "production readiness security checklist", or any request to methodically audit all trust boundaries of abadge (api, web, sdk, cli, mcp, daemon, crypto, auth, db) in a loop with subagents, durable finding files, and honest saturation gating. READ-ONLY by contract — no code edits. Distinct from abadge-e2e-sweep, which tests functional correctness; this skill reasons about adversarial behaviour.

2026-05-281

live-test-matrix.md

from "punitarani/abadge"

Define and execute a comprehensive end-to-end test matrix for an abadge feature against a live local stack — not just code-level integration tests, but real CLI binary invocations, real Hono+tRPC API calls on the wrangler emulator, real Better Auth sessions, real agent bearer tokens, and real Postgres state verification. Categorize the matrix into happy paths, edge cases, adversarial scenarios, and security pentests (≥3 variations per category), track every row in a `TESTING.md` running log, and execute via a generated bash harness. Use this skill whenever the user wants thorough manual or end-to-end testing of a feature, asks to "pentest" or "adversarially test" something, says "actually test it not just code tests" or "manually run the CLI against this", asks for a test matrix with multiple categories, or wants to verify a feature works against a real running stack. Prefer this skill over ad-hoc one-off testing scripts whenever the user wants more than three or four assertions, even if they don't explicitly

2026-05-121

cli-release.md

from "punitarani/abadge"

Prepare, validate, and publish abadge CLI releases and the PRs that carry them. Use when updating the CLI release pipeline, checking changesets or versioning, dry-running release artifacts or the installer, or committing, pushing, reviewing, and merge-prepping the CLI release PR.

2026-04-041

package.json

"author": "punitarani"

"repository": "punitarani/abadge"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

name	pr-ready
description	Use when getting an abadge PR merge-ready, checking whether a branch is mergeable, resolving conflicts against main, recovering after a rebase, verifying CI is green, or shepherding a PR through checks and review comments. Triggers on "is this merge-ready", "get this PR green", "rebase onto main", "did I lose commits", "force push", "address the review comments".

PR Ready

Read the ## Git & PR workflow section in AGENTS.md if PR or CI behavior changed.

Trust These Facts

Required PR checks live in .github/workflows/ci-cd.yml.
Merge-gating jobs: changeset-check, lint, audit, typecheck, test-unit, test-integration, test-web, e2e, build-api, build-cli, build-web, db-validate.
Local equivalents: bun run lint, bun run typecheck, bun run test:cov:unit, bun run test:cov:integration, bun run --cwd apps/web test, bun run test:e2e.
Release-surface paths live in scripts/releases/registry.ts (packages cli, mcp). Touching them requires a changeset in .changeset/, or changeset-check blocks the PR.
Base branch is main. Rebase onto origin/main. The repo merges with merge commits, not squash.
"Merge-ready" means CI is green via gh pr checks, not that the diff looks right.

Use This Workflow

Snapshot before touching history. Record the tip so a bad rebase is recoverable: git rev-parse HEAD (and git reflog is always available). Never start a rebase blind.
Sync and rebase. git fetch origin && git rebase origin/main. Resolve conflicts against origin/main. Rebase in small increments, not one long chain.
Verify nothing was stripped. Compare commit count/subjects against the snapshot. If commits vanished, recover with git reflog + git cherry-pick — do not redo the work from memory.
Run the local gate. bun run lint && bun run typecheck, then the relevant test buckets. Fix failures (including SSR/build breaks — see the SSR-safe-state rule in AGENTS.md Web rules) before pushing.
Changesets. If the diff touches a release surface, add a changeset (bun run changeset) describing the bump.
Push. git push --force-with-lease (never bare --force).
Confirm CI. gh pr checks <pr> — wait for every gating job to pass.
Address review. Resolve Greptile/reviewer comments; keep replies concise; re-run the gate after changes.

Only Report Merge-Ready When

gh pr checks <pr> shows all gating jobs green (not pending, not skipped-by-error).
No commits were lost in rebase (verified against the step-1 snapshot).
Changeset present if a release surface changed.

Until all three hold, report status honestly ("CI still running", "2 checks red") — never "merge-ready".

pr-ready

PR Ready

Trust These Facts

Use This Workflow

Only Report Merge-Ready When

このリポジトリの他の Skills

このリポジトリの他の Skills

PR Ready

Trust These Facts

Use This Workflow

Only Report Merge-Ready When