/**
 * Extract nit content from CodeRabbit review bodies.
 * Parses <details><summary>... Nitpick ...</summary>...</details> blocks
 * and returns the inner content as clean text.
 */
/**
 * Extract nit content from CodeRabbit review bodies.
 * Finds all `<details>` blocks whose `<summary>` contains "Nitpick", "nitpick", or the broom emoji.
 * Returns an array of cleaned nit text strings.
 */
export declare function parseCodeRabbitNits(body: string): string[];
/**
 * Extract "outside diff range" content from CodeRabbit review bodies.
 * Finds all `<details>` blocks whose `<summary>` contains "outside the diff"
 * or "Outside diff range" (case-insensitive).
 * Returns an array of cleaned text strings.
 */
export declare function parseCodeRabbitOutsideDiff(body: string): string[];
/**
 * Extract greptile's "Comments Outside Diff" findings from its SUMMARY comment.
 *
 * Greptile renders out-of-diff findings in the standing summary comment, BELOW
 * the flowchart, anchored by the HTML-comment marker
 * `<!-- greptile_other_comments_section -->` and trailed by a `<sub>Reviews (N):
 * …</sub>` footer (mmnto-ai/totem-strategy#690; the canonical anchor). We key on
 * the MARKER — not a sampled `<details>`/header shape — because greptile EDITS
 * this comment in place: a merged/closed PR shows the marker with the content
 * already removed post-resolution, so the live findings-state cannot be
 * reverse-engineered from a closed PR (GitHub `userContentEdits` exposes edit
 * metadata, not prior bodies). Returns [] when the section is absent or empty
 * (resolved/none).
 */
export declare function parseGreptileOutsideDiff(body: string): string[];
/**
 * Combined parser for greptile SUMMARY-comment findings — the marker-anchored
 * "Comments Outside Diff" section (greptile's per-line findings post inline and
 * are handled by the thread path). See {@link parseGreptileOutsideDiff}.
 */
export declare function parseGreptileReviewFindings(body: string): Array<{
    type: 'outside-diff';
    content: string;
}>;
/** One entry from a CR review-body section, with the per-file attribution the
 * nested `<summary>path/to/file.ts (N)</summary>` block carries when present. */
export interface CrSectionEntry {
    content: string;
    file?: string;
}
/**
 * Extract ACTIONABLE entries from CodeRabbit's "Additional comments"
 * review-body section (mmnto-ai/totem#2414 specimen 2: an actionable body-only
 * finding that never becomes an inline thread — #2413's lazy-import finding).
 * The section is mostly verification notes, so an entry qualifies only when it
 * carries the finding template's severity tag; bare LGTMs never surface.
 */
export declare function parseCodeRabbitAdditionalComments(body: string): CrSectionEntry[];
/**
 * Combined parser that extracts nitpick, outside-diff, and actionable
 * body-only ("Additional comments") findings from a CodeRabbit review body,
 * returning typed results with per-file attribution where the section nests it
 * (mmnto-ai/totem#2414).
 */
export declare function parseCodeRabbitReviewFindings(body: string): Array<{
    type: 'nitpick' | 'outside-diff' | 'body-only';
    content: string;
    file?: string;
}>;
//# sourceMappingURL=parse-nits.d.ts.map