slack-qa-investigate

Investigate repository questions in read-only mode with source citations.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/jaypatrick/skills --skill slack-qa-investigate-jaypatrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-qa-investigate
Source: https://github.com/jaypatrick/skills/tree/main/slack-qa-investigate
Command: npx skills add https://github.com/jaypatrick/skills --skill slack-qa-investigate-jaypatrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly obtain evidence-based answers about codebases without altering any files, by guiding a research-focused agent to inspect code, docs, tests, and references, and to cite sources in responses.

Core Features & Use Cases

  • Read-only investigation: examine files, tests, and docs to verify claims before answering.
  • Source-cited responses: collect and reference internal documents and linked pages.
  • Non-destructive guidance: ensures no edits, commits, or deployments occur during analysis.

Quick Start

Ask the agent to investigate a repository question and provide a sourced, read-only answer.

Frequently Asked Questions about slack-qa-investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a codebase without modifying any files?

Read-only codebase research inspects code, docs, and references to provide evidence-based answers while enforcing strict non-modification constraints. This ensures no files, commits, or deployments are altered during the investigation process.

What is source-cited codebase research and how does it work?

Source-cited codebase research collects and references internal documents, code, and linked pages to verify claims before answering. The agent inspects repository files and docs to ensure responses are backed by verifiable sources.

Can I research architecture and dependencies without altering repository files?

Yes, you can research architecture and dependencies in read-only mode to answer with evidence from code and docs without altering files. The investigation enforces strict non-destructive constraints to prevent any edits or commits during analysis.

What's the best way to get evidence-based answers about codebases quickly?

The best way to get evidence-based answers about codebases quickly is to guide a research-focused agent to inspect code, docs, tests, and references in read-only mode. This enforces source citations and non-modification constraints to deliver verified responses.

Does read-only codebase investigation support verifying claims from documentation?

Yes, read-only codebase investigation supports verifying claims from documentation by examining files, tests, and docs before answering. The agent collects and references internal documents and linked pages to ensure responses are evidence-based.

When should I not use a read-only approach for repository research?

You should not use read-only repository research when you need to modify files, commit changes, or deploy updates as part of the investigation. This approach enforces strict non-modification constraints and is limited to evidence gathering and source-cited responses.