Skip to content
Skills Library
Programming · Analysis

codebase-questions

/codebase-questions

Answer questions about a repository indexed on repowise.dev with the Repowise tools. Use when the user asks what a repository contains, how its code works, where something is defined, how risky a change is, or about its code health, dead code or security findings.

Repository
repowise ↗
Licence
AGPL-3.0
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Answer questions about a repository indexed on repowise.dev with the Repowise tools. Use when the user asks what a repository contains, how its code works, where something is defined, how risky a change is, or about its code health, dead code or security findings.

Original author description

Answer questions about a repository indexed on repowise.dev with the Repowise tools. Use when the user asks what a repository contains, how its code works, where something is defined, how risky a change is, or about its code health, dead code or security findings.

How it works

  1. 1. Pick the repository
  2. 2. Pick the tool
  3. 3. Answer
  4. 4. Handle limits plainly
Original SKILL.md headings · 52 lines, 396 words
SKILL.md preview
---
name: codebase-questions
description: Answer questions about a repository indexed on repowise.dev with the Repowise tools. Use when the user asks what a repository contains, how its code works, where something is defined, how risky a change is, or about its code health, dead code or security findings.
---

# Answer questions about an indexed repository

Repowise reads the index that repowise.dev builds for each repository: the
dependency graph, git history, ownership, code health and generated
documentation. Every tool is read-only.

## 1. Pick the repository

- If the user names a repository as `owner/name`, pass it as `repo`.
- If the user means the open workspace, read its GitHub remote
  (`git remote get-url origin`) and pass that `owner/name`.
- Otherwise call `list_repos`. If it returns one indexed repository, use it.
  If it returns several, ask the user which one.
- If `list_repos` returns nothing, tell the user to index a repository from
  their dashboard at https://repowise.dev/dashboard, then ask again.

## 2. Pick the tool

| The user wants | Tool |
|---|---|
| What the repository is and how it is laid out | `get_overview` |
| How something works end to end | `get_answer` |
| A symbol, file path or literal | `search_codebase`, then `get_symbol` for one symbol |
| Callers, callees and context for a file or symbol | `get_context` |
| How risky it is to edit files | `get_risk` |
| The risk of a commit that is already indexed | `get_change_risk` |
| Why code is shaped the way it is | `get_why` |
| Code health scores and findings | `get_health` |
| Unused code | `get_dead_code` |
| Dependency CVEs and exposed secrets | `get_security` |

Ask one question per `get_answer` call. Start with the narrowest tool that
answers the question. Before editing a file, call `get_risk` on it and read the
files it names as usually changing together.

## 3. Answer

- Cite the file paths, symbols and line ranges the tools return, then open
  those files in the workspace when the task needs the exact code.
- The index reflects the last indexed commit. When the local checkout is ahead
  of it, trust the local file for its current contents.
- Do not invent files, owners or numbers that the tools did not return.

## 4. Handle limits plainly

- If a tool says the repository is not found or not accessible, say that it is
  not indexed on repowise.dev or not shared with this account. Do not guess
  what it contains.
- If a tool says a feature is not available for the account, say so in one
  sentence and do not retry.

Versions

The database has no other skills named codebase-questions.

Database snapshot: 13.11.2026 · package version 61bb46432655 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90codebase-exploration
    Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source.
  • 90dead-code-cleanup
    Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size, or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when discussing technical debt, code hygiene, or repository maintenance.
  • 90wiki-qa
    Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.
  • 100wiki-qa
    Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks \"how does X work\" or \"where is Y defined\".
  • 100glia
    Answer structural questions about a codebase with the glia CLI, no MCP server needed. Use it for where X is defined, what changing X (or a diff) affects, how feature Y flows across services, what calls, serves or implements X, what X writes or sends, which tests cover a change,…
  • 90paparats-search
    Use when answering a question about code in the user's indexed repositories — where something is implemented, how a flow works, who calls a function, or what a change would affect. Explains when to use Paparats semantic search and when a text search is the better tool.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.