AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Q Setup Approve

skill-jlong-quiddity-q-setup-approve · by jlong

Generate a custom /approve skill for your project. Ensures your source control, CI, and PR conventions are configured via /q-which-tools, then writes a tailored skill that verifies checks and merges approved PRs.

↗ Repository
— No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-jlong-quiddity-q-setup-approve

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jlong-quiddity-q-setup-approve)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Q Setup Approve? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Setup /approve

You are generating a custom /approve skill for the user's project.

Required categories

This skill needs the following tools.json categories: source-control, ci, pr

Process

  1. Ensure tools are configured. Check if .quiddity/tools.json exists and

contains the source-control, ci, and pr categories. For any missing categories, run /q-which-tools with those categories (e.g., /q-which-tools source-control ci pr).

  1. Read the configuration. Load all available Quiddity context:
  • .quiddity/project.md — project structure, CI/CD configuration
  • .quiddity/process.md — merge strategy, review requirements,

post-merge workflow

  • .quiddity/tools.json — extract the source-control, ci, and

pr categories

  1. Ask skill-specific questions not covered by tools.json:
  • Should the skill accept a PR number as an argument? (e.g., /approve 123)

Or default to the current branch's PR?

  • What should happen after merge? (update issue status, notify, etc.)
  • Should it verify that all review comments are resolved?
  • Any post-merge cleanup steps? (delete local branch, pull latest, etc.)
  1. Generate the skill. Write a complete /approve SKILL.md to the

project's skills directory. The generated skill should:

  • Accept an optional PR number argument (defaulting to current branch's PR)
  • Verify all CI checks pass
  • Verify no unresolved review comments (if configured)
  • Verify required approvals are met
  • Perform the merge using the configured strategy (squash, merge, rebase)
  • Update the linked issue status (e.g., move to "Done" or "Shipped")
  • Clean up the branch if configured
  • Report clearly if anything blocks the merge
  • Reference .quiddity/tools.json for all tool-specific configuration
  1. Show the generated skill to the user and ask for confirmation before

finalizing.

Generated skill template

The generated /approve skill should follow this general structure, adapted to the user's specific tools:

---
name: approve
description: Verify checks and merge an approved PR.
argument-hint: "[pr-number]"
---

# /approve

[Instructions tailored to the user's source control, CI checks,
merge strategy, and post-merge workflow.]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools