Indexed The index holds package records for this repository. The package count is historical registry records; it does not mean those packages are available now.
Repository
Canonical name
getsentry/toolkit
GitHub repository ID
957245447
Package records
20 (historical registry records, not current availability)
Discovery and queue
First recorded source
alias:getsentry/sentry-mcp
Discovered
Queue state
ok
Recorded errors
0
Last settled processing
Next-check eligibility
Eligible from
The first recorded source is what the queue stored first, not the full discovery history. The error count increases when processing ends in the error state and resets after a successful settlement; it is not a count of all attempts. “Last settled processing” is when it finished, not when it started.
Eligibility is calculated as of . It is not a schedule: each collector run handles only a limited number of sources, and being eligible does not promise when a check happens.
Last saved scan
Repository metadata read
Scan status
complete
Scan saved
Extractor version
2
Continuation record
None
The scan record is separate from the queue state: the queue state shows processing progress, the scan record shows what was last saved. A continuation record only means unfinished state is stored; it has no remaining count.
Source-file evidence coverage
Raw counts of the pinned source files that stored package versions reference in this repository. They show what has been recorded, not how complete the repository is.
Scope and limits
Counts distinct pinned file links (repository, commit, path) across all stored versions, from any package, that name exactly this repository's canonical name. Files of packages owned by this repository are not counted unless some version links to them here. Alias names are not merged and no history is guessed from a current name.
“Known” means a regular-file identity is recorded. It does not mean a whole directory or package is covered. Links that are not valid pinned file URLs are not counted.
32 pinned source files referenced
32 known
0 absent at commit
0 file listing truncated
0 unsupported
0 not recorded
0 read failed
Deduplicated by repository, commit and path; the same path at two commits counts as two file identities. These are not component-group counts.
Failed source-commit reads 0
No source commit has a stored failed read for files that are still unrecorded.
Linked packages 20
Linked by verified repository identity. The count is historical registry records, not current availability.
Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.
Review code for correct logging and error handling patterns. Use when reviewing code that handles errors, uses logging functions, or captures exceptions. Enforces the error hierarchy where 4xx errors are never logged to Sentry and 5xx erro…
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Alias for sentry-skills:skill-writer. Use when users explicitly ask for "skill-creator" or reference the legacy skill name. Redirects to the canonical skill authoring workflow.
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
When last recorded, these names pointed to this repository. This is a recorded resolution, not a live GitHub check; packages and metadata are never merged because of it.