Verify claims against source code, documentation, git history, and external evidence.
npx skills add https://github.com/supertyrelle/pelley --skill verify-supertyrelle
Please help me install this Agent Skill. Skill: verify Source: https://github.com/supertyrelle/pelley/tree/main/skills/verify Command: npx skills add https://github.com/supertyrelle/pelley --skill verify-supertyrelle
This Skill checks claims against source code, documentation, git history, and external evidence so you can separate confirmed facts from speculation.
Use the verify skill to check whether the claim that the repository supports idempotent installs is true and cite the evidence.
High-intent search queries and answers about installing and using this skill.
Fact-checking documentation claims against source code and git history involves inspecting repository files and commit logs to classify assertions as verified, refuted, or uncertain. This process attaches specific evidence references to each claim for provenance-aware confidence scoring.
Provenance-aware confidence scoring is a verification method that evaluates claims against repository files, commit history, and web sources. It classifies each claim as verified, refuted, or uncertain while attaching specific evidence references to ensure downstream work can trust the result.
Verifying if a function exists in a repository using git history requires inspecting commit logs and source files to find evidence of the function's implementation. Claims are then classified as verified, refuted, or uncertain based on the discovered evidence.
External web lookup can verify research findings in a codebase by supplementing repository reads and history inspection. This optional capability allows the verification process to classify claims as verified, refuted, or uncertain using external evidence sources.
The best way to confirm a teammate's claim that a code change was made is to inspect git history and source code for evidence. This verification process classifies the claim as verified, refuted, or uncertain and attaches specific evidence references to the result.
You should not rely on source code alone for claim verification when documentation assertions or research findings require external validation. Optional web lookup supplements repository reads and git history inspection to classify claims as verified, refuted, or uncertain.
26mitch26Analyze Git commit history to generate engineering retrospective reports.
LazyIsEfficientInventory equations and claims, assign IDs, and classify verdicts.
fabioc-alohaScaffold technical documentation projects with templates for API endpoints and guides.
johannesfritzRun integration tests across services to validate end-to-end behavior.
