Skip to content

wellwelwel/lagune / .claude/skills/ingest

ingest

Verified

Use before reading any .txt file, whatever its name, and whenever a task builds on GitIngest digests. Checks whether a file is a digest (a whole repository in one file) and surveys, searches, and reads it without loading it whole. Returns only the requested lines, with token estimates and anchors for a reusable synthesis.

tools/commands/anchors.ts

View on GitHub
import type { CitedAnchor, Command, Digest } from '../types.ts';
import { readFile } from 'node:fs/promises';
import { parseAnchor } from '../anchor.ts';
import { fail } from '../fail.ts';
import { formatCount } from '../format.ts';
import { stripRoot } from '../paths.ts';

const ANCHOR_SPAN = /`([^`\s:]{1,512}:[^`\s]{1,15})`/g;

const citedAnchors = (document: string): CitedAnchor[] =>
  [...document.matchAll(ANCHOR_SPAN)].map((match) => ({
    text: match[0],
    anchor: parseAnchor(match[1]),
  }));

const anchorProblem = (
  digests: Digest[],
  { text, anchor }: CitedAnchor
): string | null => {
  if (anchor === null) return `${text}: invalid line range`;

  const entry = digests
    .map((digest) => digest.byPath.get(stripRoot(digest, anchor.path)))
    .find((found) => found !== undefined);

  if (entry === undefined) return `${text}: no such file`;
  if (entry.kind !== 'text') return `${text}: ${entry.kind} file`;

  const end = anchor.range.end ?? anchor.range.start;

  return end > entry.lines.length
    ? `${text}: the file has ${entry.lines.length} lines`
    : null;
};

export const anchors: Command = async (digests, options) => {
  const document = await readFile(
    options.synthesis ?? fail('anchors needs --synthesis'),
    'utf8'
  );
  const cited = citedAnchors(document);
  const problems = cited.flatMap((citation) => {
    const problem = anchorProblem(digests, citation);

    return problem === null ? [] : [`  ${problem}`];
  });

  if (problems.length > 0) process.exitCode = 1;

  return [
    `${formatCount(cited.length)} anchors, ${formatCount(problems.length)} broken`,
    ...problems,
  ];
};
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall