Explore a Codebase with Graphify
Build and query a local graph with the Graphify-Labs project, trace source-backed paths, and check inferred or stale relationships directly in the repository.
Identify the product from the project installation, the connected tool manifest, or the repository referenced by the user. This workflow applies to `Graphify-Labs/graphify`, the codebase graph project with a local CLI and an optional hosted offering. Confirm the installed command version and follow its own help and official documentation. A bare product name in a search request is evidence of interest, with no guarantee about a specific deployment or tool interface. ## Key Points - [Graphify-Labs open-source repository](https://github.com/Graphify-Labs/graphify) - [Graphify product documentation](https://docs.graphify.com/)
skilldb get github-repository-research-skills/graphify-codebase-graphsFull skill: 30 linesExplore a Codebase with Graphify
Confirm which Graphify the task uses
Identify the product from the project installation, the connected tool manifest, or the repository referenced by the user. This workflow applies to Graphify-Labs/graphify, the codebase graph project with a local CLI and an optional hosted offering. Confirm the installed command version and follow its own help and official documentation. A bare product name in a search request is evidence of interest, with no guarantee about a specific deployment or tool interface.
Pick an authorized repository and pin the revision. Decide what can enter the graph. Source files, docs, SQL, and configuration can contain proprietary details, even when the graph contains no verbatim source. Review exclusions and where graph artifacts and query logs are written. Keep restricted paths out of the input and keep graph reports within the approved storage boundary. For an unfamiliar install, begin with a small repository fixture and run the documented local build for that version.
Ask a question with a verifiable path
Start from a user action or code entry point you can name. For example, ask how an order cancellation request reaches storage. Use graphify query to narrow the likely subgraph and graphify path to inspect connections between two known nodes where the installed version supports those commands. Resolve ambiguous symbols with a package or path. The working tree may contain multiple routes with the same name and several adapters with different runtime bindings.
Verify the weakest edge against source. Graphify documents distinctions between extracted and inferred edges. Read the source for imports, call sites, dependency injection, environment-dependent selection, and tests before treating a graph path as a runtime call path. Inspect actual dispatch registration when a link depends on a framework. If the graph cannot explain how it obtained a link, mark it as unverified. Dynamic routing, plugins, generated modules, and code excluded from indexing can all create gaps.
Reconcile the graph with the current source
Record which revision and input paths generated the graph and compare those with the working tree. If the code changed, update the graph using the project's documented local workflow or continue with direct source reads. A missing path can mean no graph evidence rather than no relationship. Test this with a fixture where a route has moved but the graph has not been refreshed.
Report the starting question, graph revision, nodes and important edge evidence, and file or symbol references checked. Distinguish extracted, inferred, and unresolved links. Leave project hooks, host integration, graph sharing, and any hosted index changes to the user's established workflow.
References
Install this skill directly: skilldb add github-repository-research-skills
Related Skills
Reading an Unfamiliar Codebase
Activate this skill when the user has to understand a codebase they did not write: onboarding to a new repository, evaluating a library's internals before adopting it, tracing how a request flows through a service, or figuring out where to make a change in a large project. Triggers on keywords like "understand this codebase," "where is the entry point," "how does this repo work," "trace a request," "code reading," "navigate a large codebase," "ripgrep," "ctags," "folder structure," and "onboarding to a repository." Covers entry points, build files, folder mapping, end-to-end tracing, reading tests as documentation, tooling, and time-boxed exploration.
Repository Health Assessment
Activate this skill when the user is evaluating whether an open-source project on GitHub is safe to depend on, doing "github repository research" before adopting a library, or asking whether a project is maintained, abandoned, or risky. Triggers on keywords like "repository health," "is this repo maintained," "bus factor," "release cadence," "issue response time," "abandoned project," "dependency due diligence," "open source risk," "CI status," "license check," and "security policy." Covers a scored health checklist, the signals that actually predict maintenance, and the red flags that should end an evaluation early.
Repository Security Posture
Activate this skill when the user needs to judge how well a GitHub repository defends itself and its downstream users: whether secrets have leaked into history, whether its GitHub Actions workflows can be hijacked, whether the default branch is protected, how dependencies are updated, whether commits and releases are signed, and whether there is a working vulnerability disclosure process. Triggers on keywords like "security posture," "secrets in git history," "pull_request_target," "pin actions to SHA," "branch protection," "dependabot," "renovate," "signed commits," "SECURITY.md," "supply chain attack," "OpenSSF Scorecard," and "workflow permissions." Covers history scanning, Actions supply-chain risks, protection rules, update automation, signing, and disclosure policy.
Reproducing a Research Repository
Activate this skill when the user is trying to run the code released with an academic paper or a research prototype and get results that match the claims: setting up a pinned environment, mapping the paper's equations and tables to the code, handling datasets and random seeds, and writing up a reproduction that others can trust. Triggers on keywords like "reproduce this paper," "research code," "reproducibility," "paper vs code," "random seed," "can't match the reported numbers," "replication," "pin the environment," "ML reproducibility," and "reproduction report." Covers environment pinning, reading the paper against the code, datasets and seeds, running the smallest experiment first, documenting deviations, and honest reporting.
Comparing Repositories for Adoption
Activate this skill when the user must choose between several open-source libraries, frameworks, or tools for the same job and wants a defensible comparison rather than a popularity contest: weighing API fit, maintenance, performance, community, license, and the cost of leaving later, and recording the decision so it can be revisited. Triggers on keywords like "compare libraries," "which should we adopt," "library evaluation," "decision matrix," "architecture decision record," "ADR," "exit cost," "vendor lock-in," "build vs buy vs adopt," "technology selection," and "candidate comparison." Covers criteria definition, spikes, weighted scoring with sensitivity checks, exit-cost estimation, and a decision record template.
Contributing and the First Pull Request
Activate this skill when the user wants to contribute to an open-source project they do not maintain: filing an issue well, preparing a first pull request that gets merged, matching the project's conventions, handling review feedback, and deciding when to fork instead. Triggers on keywords like "first pull request," "contributing to open source," "CONTRIBUTING.md," "how to file an issue," "PR etiquette," "code review feedback," "DCO sign-off," "CLA," "changelog entry," "upstream a fix," and "fork or contribute." Covers reading contribution guidelines, issue etiquette, scoping small PRs, style and tests, changelog practice, responding to review, and the fork decision.