Researching Codebase
Investigates codebase before planning. Use before any non-trivial implementation task to gather context in isolation.
Install
$ agentstack add skill-qte77-claude-code-plugins-researching-codebase ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qte77-claude-code-plugins-researching-codebase) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Codebase Research (ACE-FCA)
Query: $ARGUMENTS
Gathers codebase context in isolation before planning. Prevents search artifacts from polluting main context.
Core Principles
- Documentation-only - Describe what exists, where, and how it works
- No evaluations - Never suggest improvements or critique implementation
- Evidence-based - Provide file paths, line numbers, and code references
- Isolation - Research runs in fork context; return only distilled findings
When to Use
- Before planning non-trivial implementations
- When unfamiliar with relevant codebase areas
- Before architectural decisions
Workflow
- Read mentioned files first - If specific files mentioned, read completely before exploring
- Decompose the question - Break query into researchable components
- Explore codebase - Investigate architecture, patterns, constraints
- Identify scope - Determine relevant areas based on findings
- Distill - Return structured summary using output format below
Output Format
Follow ACE-FCA quality equation: Correct + Complete + Minimal noise
---
research_query: ""
timestamp: ""
files_examined:
---
## Key Files
| File | Purpose | Key Lines |
|------|---------|-----------|
| `path/to/file.ext` | Brief purpose | L42-58 |
## Patterns
- **Pattern name**: Description with file reference (`path:line`)
## Constraints
- Constraint with evidence (`path:line`)
Evidence Requirements
Every claim must include:
- File path: Exact location (
src/auth/login.ts) - Line numbers: Specific lines (
L42-58orL127) - Code reference: Function/class name when relevant
Bad: "Authentication uses JWT tokens" Good: "Authentication uses JWT tokens (src/auth/jwt.ts:L23-45, verifyToken function)"
References
See references/context-management.md and references/core-principles.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qte77
- Source: qte77/claude-code-plugins
- License: Apache-2.0
- Homepage: https://qte77.github.io/claude-code-plugins/
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.