# Q Which Tools

> Discover what tools a project uses and save the configuration to .quiddity/tools.json. Pass category names as arguments (e.g., /q-which-tools issues source-control).

- **Type:** Skill
- **Install:** `agentstack add skill-jlong-quiddity-q-which-tools`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [jlong](https://agentstack.voostack.com/s/jlong)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [jlong](https://github.com/jlong)
- **Source:** https://github.com/jlong/quiddity/tree/main/skills/q-which-tools

## Install

```sh
agentstack add skill-jlong-quiddity-q-which-tools
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# /q-which-tools

You are interviewing the user about the tools their project uses. Your job is
to ask about each requested category and write the results to
`.quiddity/tools.json`.

## Arguments

`$ARGUMENTS` contains space-separated category names. Supported categories:

- **issues** — Issue/task tracker (Linear, GitHub Issues, Jira, etc.)
- **source-control** — Source control host (GitHub, GitLab, Bitbucket, etc.)
- **ci** — Continuous integration (GitHub Actions, CircleCI, etc.)
- **pr** — Pull request conventions (merge strategy, review requirements, etc.)
- **deploy** — Deployment target (Vercel, AWS, Fly, manual, etc.)
- **notifications** — Notification channels (Slack, Discord, email, etc.)

If no arguments are provided, ask the user which categories they'd like to
configure.

## Process

1. **Read process context.** Check if `.quiddity/process.md` exists. If it does,
   read it to understand the user's SDLC. Use this context to inform your
   questions and pre-fill answers where possible (e.g., if the process doc
   mentions "we use GitHub flow", you already know the source-control platform).

2. **Read existing config.** Check if `.quiddity/tools.json` exists. If it does,
   read it and note which categories are already configured.

3. **For each requested category:**
   - If the category already exists in tools.json, tell the user it's already
     configured and show the current value. Ask if they want to reconfigure it.
     If not, skip it.
   - If the category is new, ask the user what tool they use.
   - Ask follow-up questions specific to the tool they selected. See the
     category reference below for what to ask.

4. **Write the results.** Merge the new category data into `.quiddity/tools.json`.
   Create the `.quiddity/` directory if it doesn't exist. Preserve any existing
   categories that weren't reconfigured.

## Category reference

### issues

Ask:
- Which issue tracker? (Linear, GitHub Issues, Jira, Shortcut, etc.)
- Team or project name?
- What states/statuses do issues move through? (e.g., Todo → In Progress → Done)
- How is priority represented? (priority field, labels, columns, etc.)
- Any label conventions?

Example output:
```json
{
  "issues": {
    "tool": "linear",
    "team": "ENG",
    "states": {
      "backlog": "Backlog",
      "todo": "Todo",
      "inProgress": "In Progress",
      "done": "Done",
      "cancelled": "Cancelled"
    },
    "priorities": ["Urgent", "High", "Medium", "Low", "None"],
    "labels": ["bug", "feature", "chore", "improvement"]
  }
}
```

### source-control

Ask:
- Which platform? (GitHub, GitLab, Bitbucket, etc.)
- Default/base branch name? (main, master, develop, etc.)
- Branch naming convention? (e.g., `feat/LIN-{{id}}-{{slug}}`, `feature/JIRA-{{id}}`)
- Commit message format? (conventional commits, free-form, etc.)

Example output:
```json
{
  "source-control": {
    "tool": "github",
    "baseBranch": "main",
    "branchFormat": "feat/LIN-{{id}}-{{slug}}",
    "commitFormat": "conventional"
  }
}
```

### ci

Ask:
- Which CI system? (GitHub Actions, CircleCI, Jenkins, etc.)
- What checks run on PRs? (tests, linting, type checking, build, etc.)
- How to run those checks locally? (e.g., `npm test`, `make check`)

Example output:
```json
{
  "ci": {
    "tool": "github-actions",
    "checks": ["tests", "lint", "typecheck", "build"],
    "localChecks": ["npm test", "npm run lint", "npm run typecheck", "npm run build"]
  }
}
```

### pr

Ask:
- Merge strategy? (squash, merge commit, rebase)
- Delete branch after merge?
- Required number of approvals?
- Any PR template in the repo?
- PR title format?

Example output:
```json
{
  "pr": {
    "mergeStrategy": "squash",
    "deleteBranch": true,
    "requiredApprovals": 1,
    "hasTemplate": true,
    "titleFormat": "conventional"
  }
}
```

### deploy

Ask:
- Where does the project deploy? (Vercel, AWS, Fly.io, Heroku, manual, etc.)
- Is deployment automatic on merge to the base branch?
- Any manual steps?

Example output:
```json
{
  "deploy": {
    "tool": "vercel",
    "automatic": true,
    "trigger": "merge-to-main"
  }
}
```

### notifications

Ask:
- Where should notifications go? (Slack, Discord, email, none)
- Which channel/room?
- What events should trigger notifications?

Example output:
```json
{
  "notifications": {
    "tool": "slack",
    "channel": "#engineering",
    "events": ["pr-merged", "deploy-complete"]
  }
}
```

## Source & license

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

- **Author:** [jlong](https://github.com/jlong)
- **Source:** [jlong/quiddity](https://github.com/jlong/quiddity)
- **License:** MIT

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jlong-quiddity-q-which-tools
- Seller: https://agentstack.voostack.com/s/jlong
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.