update_vettedpositions

Align .vettedpositions entries with goanalysis output after line-number changes.

2.0k|126|Updated Jun 16, 2020
One-click install
npx skills add https://github.com/authgear/authgear-server --skill update-vettedpositions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update_vettedpositions
Source: https://github.com/authgear/authgear-server/tree/main/.claude/skills/update_vettedpositions
Command: npx skills add https://github.com/authgear/authgear-server --skill update-vettedpositions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the .vettedpositions file accurate when goanalysis only shifts line numbers without introducing new issues, preventing stale offsets from persisting in reports.

Core Features & Use Cases

  • Line-number drift detection: Compare goanalysis output against existing vetted positions and act only when the warning is purely a positional move.
  • Safe maintenance workflow: Rerun goanalysis, sort the vetted list, and commit changes to maintain trust in vetted data without masking genuine warnings.
  • Use Case: After reformatting or minor refactors bump line numbers, update .vettedpositions so automation reports stay clean while preserving previously approved warnings.

Quick Start

Run the update_vettedpositions procedure to refresh .vettedpositions whenever goanalysis reports only line-number shifts.

Frequently Asked Questions about update_vettedpositions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update vetted positions after line numbers shift in Go code?

To update vetted positions after line numbers shift, run goanalysis and make sort-vettedpositions to align .vettedpositions entries with the new warning locations, ensuring stale offsets are removed before committing.

Why does goanalysis report line-number drift after a minor Go refactor?

Line-number drift occurs when minor refactoring shifts code positions without introducing new issues. goanalysis detects these positional moves, requiring .vettedpositions updates to preserve previously approved warnings without masking genuine new reports.

How do I keep .vettedpositions accurate during Go repository maintenance?

Keep .vettedpositions accurate by running the update procedure to compare goanalysis output against existing entries, sort the vetted list, and commit changes that refresh stale offsets while maintaining trust in vetted data.

When should I rerun goanalysis to sync vetted positions?

Rerun goanalysis to sync vetted positions whenever code reformatting or minor refactors bump line numbers, ensuring .vettedpositions reflects current locations and automation reports stay clean without hiding genuine warnings.

Does updating .vettedpositions mask new Go code analysis warnings?

Updating .vettedpositions does not mask new warnings. The procedure detects harmless line drift by comparing reported positions against previous entries, acting only on positional moves while preserving genuine goanalysis warnings.

What is the safe maintenance workflow for goanalysis vetted positions?

The safe maintenance workflow involves running goanalysis, executing make sort-vettedpositions to order the list, and committing changes to maintain accurate vetted data without masking genuine code warnings.