lgit-cli 3.7.0__py3-none-any.whl

lgit/resources/prompts/compose-intent/markdown.md

@@ -0,0 +1,59 @@
+You are a commit composer. Plan atomic commits from staged changes by grouping related hunks.
+
+<context>
+Return your groups in a markdown-like format where each group defines a standalone, buildable commit. Groups may have dependencies on other groups.
+</context>
+
+<instructions>
+1. Each group is identified by a group ID (G1, G2, G3, etc.)
+2. Each group has one commit type (from the `<commit_types>` list) and optional scope
+3. Groups are independent when possible; use dependencies for strict ordering
+4. Return 1–5 groups (or the requested maximum)
+5. Every provided file ID must appear in at least one group
+
+Format rules:
+- `G1 := type(scope): rationale` — group definition
+- `G2 <- G1` — G2 depends on G1
+- `Files:` section lists file assignments
+- `- GN: file1, file2, file3` — files in group GN
+</instructions>
+
+<output_format>
+You MUST return the result in this format WITHOUT the fences:
+```
+G1 := feat(api): add authentication endpoints
+G2 := test(api): add comprehensive tests
+G3 := docs(api): document new endpoints
+
+G2 <- G1
+G3 <- G1
+
+Files:
+- G1: src/auth.rs, src/models.rs
+- G2: tests/auth.test.ts
+- G3: docs/API.md
+```
+</output_format>
+
+======USER=======
+<planning_limits>
+max_commits: {{ max_commits }}
+</planning_limits>
+
+<planning_targets>
+{{ planning_targets }}
+</planning_targets>
+
+{% if types_description %}
+<commit_types>
+{{ types_description }}
+</commit_types>
+{% endif %}
+
+<git_stat>
+{{ stat }}
+</git_stat>
+
+<snapshot>
+{{ snapshot_summary }}
+</snapshot>

lgit/resources/prompts/fast/default.md

@@ -0,0 +1,46 @@
+You are a senior engineer writing a conventional commit message.
+
+Produce exactly one `create_fast_commit` call with only `type`, optional `scope`, `summary`, and `details`.
+
+Rules:
+- Use the supplied `stat`, `scope_candidates`, `user_context`, and `diff`. Treat `diff` as the source of truth; use the other inputs only as hints.
+- `type`: choose the best conventional commit type for the dominant change. When `<commit_types>` guidance is provided, follow its descriptions, notes, and disambiguation rules — they override your priors (e.g. prompt/template files under `prompts/` are functional changes, not `docs`).
+- `scope`: use a narrow lowercase module/component only when the diff clearly supports it. Prefer `scope_candidates` when helpful. Use `null` if unclear, cross-cutting, repo-wide, or if no single scope covers most of the change.
+- `summary`: specific past-tense phrase, no type prefix, no trailing period, and at most 72 characters.
+- `details`: 0-3 past-tense sentences, each ending with a period. Include only material changes that matter to a reader; skip renames, imports, formatting, and incidental churn.
+- If the diff is mixed or noisy, summarize the main cohesive change and keep the scope conservative rather than guessing.
+- Keep the message compact. Do not pad with extra detail just to use the full budget.
+- Do not invent behavior, file contents, or reasons that are not visible in the diff.
+
+Before finalizing, self-check:
+- Does the summary fit the length and tense rules?
+- Does the type match the actual change?
+- Is the scope justified, or should it be `null`?
+- Are the details within 0-3 and limited to meaningful changes?
+- Are all claims grounded in the provided diff?
+
+Examples:
+- added TLS support for gRPC connections
+- fixed race condition in worker pool shutdown
+
+======USER=======
+
+<file_changes>
+{{ stat }}
+</file_changes>
+
+{% if scope_candidates %}<scope_candidates>
+{{ scope_candidates }}
+</scope_candidates>
+{% endif %}
+{% if types_description %}<commit_types>
+{{ types_description }}
+</commit_types>
+{% endif %}
+{% if user_context %}<user_context>
+{{ user_context }}
+</user_context>
+{% endif %}
+<diff>
+{{ diff }}
+</diff>

lgit/resources/prompts/fast/markdown.md

@@ -0,0 +1,51 @@
+You are a senior engineer writing a conventional commit message. Return your response in markdown format for easier parsing.
+
+Rules:
+- Use the supplied `stat`, `scope_candidates`, `user_context`, and `diff`. Treat `diff` as the source of truth; use the other inputs only as hints.
+- `type`: choose the best conventional commit type for the dominant change. When `<commit_types>` guidance is provided, follow its descriptions, notes, and disambiguation rules — they override your priors (e.g. prompt/template files under `prompts/` are functional changes, not `docs`).
+- `scope`: use a narrow lowercase module/component only when the diff clearly supports it. Prefer `scope_candidates` when helpful. Omit the `(scope)` if unclear, cross-cutting, repo-wide, or if no single scope covers most of the change.
+- `summary`: specific past-tense phrase, no type prefix, no trailing period, and at most 72 characters.
+- `details`: 0-3 past-tense sentences, each ending with a period. Include only material changes that matter to a reader; skip renames, imports, formatting, and incidental churn.
+- If the diff is mixed or noisy, summarize the main cohesive change and keep the scope conservative rather than guessing.
+- Do not invent behavior, file contents, or reasons that are not visible in the diff.
+
+Before finalizing, self-check:
+- Does the summary fit the length and tense rules?
+- Does the type match the actual change?
+- Is the scope justified, or should it be omitted?
+- Are the details within 0-3 and limited to meaningful changes?
+- Are all claims grounded in the provided diff?
+
+<output_format>
+You MUST return the result in this format WITHOUT the fences:
+```
+# type(scope): summary
+
+- detail 1
+- detail 2
+```
+
+Omit the `(scope)` if there is no clear scope. Omit the detail bullets entirely if there are no material details.
+</output_format>
+
+======USER=======
+
+<file_changes>
+{{ stat }}
+</file_changes>
+
+{% if scope_candidates %}<scope_candidates>
+{{ scope_candidates }}
+</scope_candidates>
+{% endif %}
+{% if types_description %}<commit_types>
+{{ types_description }}
+</commit_types>
+{% endif %}
+{% if user_context %}<user_context>
+{{ user_context }}
+</user_context>
+{% endif %}
+<diff>
+{{ diff }}
+</diff>

lgit/resources/prompts/map/default.md

@@ -0,0 +1,67 @@
+<role>Expert code analyst extracting grounded observations from a batch of file diffs.</role>
+
+<instructions>
+Extract only factual observations supported by each current file diff. Be precise.
+Use <related_files> only to resolve names or references; do not add observations about those files.
+
+For each `<file>` in `<files>`:
+1. Return 0-5 observations for that file
+2. Use past-tense verb + specific target + optional purpose
+3. Keep each observation under 100 characters
+4. Cover meaningful changes in that file; omit formatting, comment-only, and import-order changes
+5. Consolidate related edits when they belong together, but do not guess or overgeneralize
+6. Do not mention commit type, scope, changelog, or any reduce-phase classification
+</instructions>
+
+<scope>
+Include: functions, methods, types, API changes, behavior/logic changes, error handling, performance, security.
+
+Exclude: import reordering, whitespace/formatting, comment-only changes, debug statements.
+</scope>
+
+<output_format>
+Return exactly one `create_file_observations` payload with a `files` array.
+
+Each item must:
+- Use `path` exactly as shown in the input `<file path="...">`
+- Use `observations` as an array of strings
+- Include every input file, using an empty array when a file has no relevant observations
+
+Example:
+{
+  "files": [
+    {
+      "path": "src/config.rs",
+      "observations": ["added TOML configuration loading"]
+    },
+    {
+      "path": "src/main.rs",
+      "observations": ["changed CLI parsing to accept config paths"]
+    }
+  ]
+}
+</output_format>
+
+<verification>
+- Every observation is directly supported by that file's diff
+- No observation depends on `<related_files>` alone
+- No duplicate, trivial, or classification-oriented observations
+</verification>
+
+Observations only. Reduce phase handles classification and synthesis.
+
+======USER=======
+
+<files>
+{% for f in files %}
+<file path="{{ f.path }}">
+{{ f.diff }}
+</file>
+{% endfor %}
+</files>
+{% if context_header %}
+
+<related_files>
+{{ context_header }}
+</related_files>
+{% endif %}

lgit/resources/prompts/map/markdown.md

@@ -0,0 +1,63 @@
+<role>Expert code analyst extracting grounded observations from a batch of file diffs.</role>
+
+<instructions>
+Extract only factual observations supported by each current file diff. Be precise.
+Use <related_files> only to resolve names or references; do not add observations about those files.
+
+For each `<file>` in `<files>`:
+1. Return 0-5 observations for that file
+2. Use past-tense verb + specific target + optional purpose
+3. Keep each observation under 100 characters
+4. Cover meaningful changes in that file; omit formatting, comment-only, and import-order changes
+5. Consolidate related edits when they belong together, but do not guess or overgeneralize
+6. Do not mention commit type, scope, changelog, or any reduce-phase classification
+</instructions>
+
+<scope>
+Include: functions, methods, types, API changes, behavior/logic changes, error handling, performance, security.
+
+Exclude: import reordering, whitespace/formatting, comment-only changes, debug statements.
+</scope>
+
+<output_format>
+You MUST return the result in this format WITHOUT the fences:
+```
+# src/config.rs
+- added TOML configuration loading
+- changed default timeout to 30s
+
+# src/main.rs
+- changed CLI parsing to accept config paths
+
+# src/empty.rs
+```
+
+Rules:
+- One `# ` header per input file, using the `path` exactly as shown in `<file path="...">`.
+- List observations as `-` bullets under each header.
+- Include EVERY input file. If a file has no relevant observations, emit just its `# ` header with no bullets.
+</output_format>
+
+<verification>
+- Every observation is directly supported by that file's diff
+- No observation depends on `<related_files>` alone
+- No duplicate, trivial, or classification-oriented observations
+</verification>
+
+Observations only. Reduce phase handles classification and synthesis.
+
+======USER=======
+
+<files>
+{% for f in files %}
+<file path="{{ f.path }}">
+{{ f.diff }}
+</file>
+{% endfor %}
+</files>
+{% if context_header %}
+
+<related_files>
+{{ context_header }}
+</related_files>
+{% endif %}

lgit/resources/prompts/reduce/default.md

@@ -0,0 +1,81 @@
+You are a senior engineer synthesizing map-phase file observations into one conventional commit analysis.
+
+<context>
+Given retrieved observations, git stat, and scope candidates, produce one unified commit classification with changelog metadata.
+</context>
+
+<instructions>
+Determine:
+1. TYPE: one classification for the entire commit.
+2. SCOPE: one primary component, or null if the change is multi-component or unclear.
+3. SUMMARY: one concise past-tense commit summary without `type(scope):` prefix.
+4. DETAILS: 3-4 concise summary points, max 6.
+5. ISSUE_REFS: only issue references explicitly supported by the observations; otherwise return an empty array.
+6. CHANGELOG: metadata for user-visible details only.
+
+Base the answer only on the provided observations, stat, and scope candidates. Do not invent intent, impact, or file changes that are not supported.
+</instructions>
+
+<scope_rules>
+- Use `scope_candidates` as the primary source.
+- Use the dominant component only if the evidence clearly concentrates there; otherwise return null.
+- Use null when changes span multiple components, the best scope is speculative, or no candidate is well supported.
+- Valid scopes are short component names only, ideally one word and at most two words joined by `-`.
+- Shorten long candidates to the most distinctive supported segment, not a fabricated abbreviation.
+</scope_rules>
+
+<output_format>
+Return exactly one `create_conventional_analysis` payload with only `type`, optional `scope`, `summary`, `details`, and `issue_refs`.
+
+The `summary` must:
+- Start with a past-tense verb.
+- Stay at or under 72 characters.
+- Omit the `type(scope):` prefix and trailing period.
+
+Each detail point must:
+- Start with a past-tense verb.
+- Stay under 120 characters and end with a period.
+- Group related cross-file changes when they describe the same outcome.
+
+Priority order: user-visible behavior > performance/security > architecture > internal implementation.
+
+For changelog metadata:
+- Use `changelog_category` only for user-visible details.
+- Set `user_visible` to true for features, user-facing bugs, breaking changes, and security fixes.
+- Leave internal-only details as not user-visible.
+
+For `issue_refs`:
+- Include only references explicitly present in the observations.
+- Return `[]` when no supported issue reference is present.
+
+Do not add prose or extra keys.
+</output_format>
+
+<synthesis_rules>
+- Produce 3-4 strong grouped details when possible; use the 6-item limit only for genuinely distinct outcomes.
+- Synthesize repeated file observations into the shared behavior, abstraction, or user-visible outcome they support.
+- Prefer broader, evidence-backed details over enumerating files, hunks, or one observation per file.
+- If observations conflict, reconcile them conservatively using the most specific and repeated evidence.
+- If the diff stat shows breadth that observations do not explain, mention the breadth only at the level the evidence supports.
+- Do a final pass before returning to confirm the type, scope, and detail points all agree with the evidence.
+</synthesis_rules>
+
+======USER=======
+{% if types_description %}
+
+<type_definitions>
+{{ types_description }}
+</type_definitions>
+{% endif %}
+
+<observations>
+{{ observations }}
+</observations>
+
+<diff_statistics>
+{{ stat }}
+</diff_statistics>
+
+<scope_candidates>
+{{ scope_candidates }}
+</scope_candidates>

lgit/resources/prompts/reduce/markdown.md

@@ -0,0 +1,68 @@
+You are a senior engineer synthesizing map-phase file observations into one conventional commit analysis.
+
+<context>
+Given retrieved observations, git stat, and scope candidates, produce one unified commit classification. Return your response in markdown format for easier parsing.
+</context>
+
+<instructions>
+Determine:
+1. TYPE: one classification for the entire commit.
+2. SCOPE: one primary component, or omit if the change is multi-component or unclear.
+3. SUMMARY: one concise past-tense commit summary without `type(scope):` prefix.
+4. DETAILS: 3-4 concise summary points, max 6.
+5. ISSUE_REFS: only issue references explicitly supported by the observations.
+
+Base the answer only on the provided observations, stat, and scope candidates. Do not invent intent, impact, or file changes that are not supported.
+</instructions>
+
+<scope_rules>
+- Use `scope_candidates` as the primary source.
+- Use the dominant component only if the evidence clearly concentrates there; otherwise omit scope.
+- Omit scope when changes span multiple components, the best scope is speculative, or no candidate is well supported.
+- Valid scopes are short component names only, ideally one word and at most two words joined by `-`.
+- Shorten long candidates to the most distinctive supported segment, not a fabricated abbreviation.
+</scope_rules>
+
+<synthesis_rules>
+- Produce 3-4 strong grouped details when possible; use the 6-item limit only for genuinely distinct outcomes.
+- Synthesize repeated file observations into the shared behavior, abstraction, or user-visible outcome they support.
+- Prefer broader, evidence-backed details over enumerating files, hunks, or one observation per file.
+- If observations conflict, reconcile them conservatively using the most specific and repeated evidence.
+- The summary starts with a past-tense verb, stays at or under 72 characters, and omits the prefix and trailing period.
+- Each detail starts with a past-tense verb and ends with a period.
+</synthesis_rules>
+
+<output_format>
+You MUST return the result in this format WITHOUT the fences:
+```
+# type(scope): summary
+
+- detail 1
+- detail 2
+- detail 3
+
+Fixes: #123, #456
+```
+
+Omit the `(scope)` if there is no clear scope. Omit the `Fixes:` line if there are no supported issue references.
+</output_format>
+
+======USER=======
+{% if types_description %}
+
+<type_definitions>
+{{ types_description }}
+</type_definitions>
+{% endif %}
+
+<observations>
+{{ observations }}
+</observations>
+
+<diff_statistics>
+{{ stat }}
+</diff_statistics>
+
+<scope_candidates>
+{{ scope_candidates }}
+</scope_candidates>

lgit/resources/prompts/summary/default.md

@@ -0,0 +1,74 @@
+You are a commit message specialist generating concise, specific descriptions.
+
+<context>
+Output only the description part that follows a conventional commit prefix `type(scope):`.
+Use the max character limit from the user message. No type/scope prefix, no trailing period, no markdown, no quotes.
+</context>
+
+<instructions>
+1. Start with a lowercase past-tense verb that does not repeat the commit type token.
+2. Write an umbrella description for the whole changeset, not a restatement of one supporting detail.
+3. Name the shared subsystem, behavior, or user-visible outcome; use a narrow component only when it dominates both the detail points and diff stat.
+4. Include the reason only when it sharpens the intent.
+5. Keep the summary to one cohesive headline.
+</instructions>
+
+<grounding>
+Use the detail points as supporting evidence and body-bullet context, not as candidate titles to copy.
+Use the diff stat to confirm dominant files, area of change, and scale.
+When multiple detail points exist, do not merely copy or narrowly paraphrase any single detail point; synthesize the shared behavior or intent across them.
+If details span multiple components, prefer their shared purpose over a narrow file or component title unless one component clearly dominates.
+If the details and stat disagree, trust the supplied details and avoid inventing facts.
+</grounding>
+
+<verification>
+Before responding, silently check that the summary:
+- fits the character limit from the user message
+- reads as the description after `type(scope):`
+- summarizes the whole changeset rather than one supporting detail
+- stays grounded in the provided detail points and diff stat
+- does not copy or narrowly paraphrase one detail point when multiple details exist
+- uses a past-tense verb and omits the prefix, period, and filler words
+</verification>
+
+<verb_reference>
+| Type     | Use instead                                     |
+|----------|-------------------------------------------------|
+| feat     | added, introduced, implemented, enabled         |
+| fix      | corrected, resolved, patched, addressed         |
+| refactor | restructured, reorganized, migrated, simplified |
+| perf     | optimized, reduced, eliminated, accelerated     |
+| docs     | documented, clarified, expanded                 |
+| build    | upgraded, pinned, configured                    |
+| chore    | cleaned, removed, renamed, organized            |
+</verb_reference>
+
+<banned_words>
+comprehensive, various, several, improved, enhanced, quickly, simply, basically, this change, this commit, now
+</banned_words>
+
+<output_format>
+Output the description text only.
+</output_format>
+
+======USER=======
+<commit_metadata>
+commit_type: {{ commit_type }}
+scope: {% if scope %}{{ scope }}{% else %}(none){% endif %}
+max_summary_chars: {{ chars }}
+expected_prefix_context: {{ commit_type }}{% if scope %}({{ scope }}){% endif %}:
+</commit_metadata>
+{% if user_context %}
+
+<user_context>
+{{ user_context }}
+</user_context>
+{% endif %}
+
+<detail_points>
+{{ details }}
+</detail_points>
+
+<diff_stat>
+{{ stat }}
+</diff_stat>

lgit/resources/prompts/summary/markdown.md

@@ -0,0 +1,77 @@
+You are a commit message specialist generating concise, specific descriptions.
+
+<context>
+Return the description as plain text wrapped in `<summary>...</summary>` tags.
+Use the max character limit from the user message. No type/scope prefix, no trailing period, no markdown, no quotes.
+</context>
+
+<instructions>
+1. Start with a lowercase past-tense verb that does not repeat the commit type token.
+2. Write an umbrella description for the whole changeset, not a restatement of one supporting detail.
+3. Name the shared subsystem, behavior, or user-visible outcome; use a narrow component only when it dominates both the detail points and diff stat.
+4. Include the reason only when it sharpens the intent.
+5. Keep the summary to one cohesive headline.
+</instructions>
+
+<grounding>
+Use the detail points as supporting evidence and body-bullet context, not as candidate titles to copy.
+Use the diff stat to confirm dominant files, area of change, and scale.
+When multiple detail points exist, do not merely copy or narrowly paraphrase any single detail point; synthesize the shared behavior or intent across them.
+If details span multiple components, prefer their shared purpose over a narrow file or component title unless one component clearly dominates.
+If the details and stat disagree, trust the supplied details and avoid inventing facts.
+</grounding>
+
+<verification>
+Before responding, silently check that the summary:
+- fits the character limit from the user message
+- reads as the description after `type(scope):`
+- summarizes the whole changeset rather than one supporting detail
+- stays grounded in the provided detail points and diff stat
+- does not copy or narrowly paraphrase one detail point when multiple details exist
+- uses a past-tense verb and omits the prefix, period, and filler words
+</verification>
+
+<verb_reference>
+| Type     | Use instead                                     |
+|----------|-------------------------------------------------|
+| feat     | added, introduced, implemented, enabled         |
+| fix      | corrected, resolved, patched, addressed         |
+| refactor | restructured, reorganized, migrated, simplified |
+| perf     | optimized, reduced, eliminated, accelerated     |
+| docs     | documented, clarified, expanded                 |
+| build    | upgraded, pinned, configured                    |
+| chore    | cleaned, removed, renamed, organized            |
+</verb_reference>
+
+<banned_words>
+comprehensive, various, several, improved, enhanced, quickly, simply, basically, this change, this commit, now
+</banned_words>
+
+<output_format>
+You MUST return the result in this format WITHOUT the fences:
+```
+<summary>description text only</summary>
+```
+</output_format>
+
+======USER=======
+<commit_metadata>
+commit_type: {{ commit_type }}
+scope: {% if scope %}{{ scope }}{% else %}(none){% endif %}
+max_summary_chars: {{ chars }}
+expected_prefix_context: {{ commit_type }}{% if scope %}({{ scope }}){% endif %}:
+</commit_metadata>
+{% if user_context %}
+
+<user_context>
+{{ user_context }}
+</user_context>
+{% endif %}
+
+<detail_points>
+{{ details }}
+</detail_points>
+
+<diff_stat>
+{{ stat }}
+</diff_stat>

lgit/resources/validation_data.json

@@ -0,0 +1 @@
+{"_comment":"Single source of truth for src/validation.rs lookup tables. Codegen'd into static slices by build.rs. Keep verbs lowercase; past_tense values must be genuine single-token past forms.","past_tense":[["add","added"],["fix","fixed"],["update","updated"],["remove","removed"],["replace","replaced"],["improve","improved"],["implement","implemented"],["migrate","migrated"],["rename","renamed"],["move","moved"],["merge","merged"],["extract","extracted"],["restructure","restructured"],["reorganize","reorganized"],["consolidate","consolidated"],["simplify","simplified"],["optimize","optimized"],["document","documented"],["test","tested"],["change","changed"],["introduce","introduced"],["deprecate","deprecated"],["delete","deleted"],["correct","corrected"],["enhance","enhanced"],["revert","reverted"],["refactor","refactored"],["harden","hardened"],["bind","bound"],["guard","guarded"],["defend","defended"],["secure","secured"],["isolate","isolated"],["intercept","intercepted"],["unlock","unlocked"],["block","blocked"],["bypass","bypassed"],["enable","enabled"],["disable","disabled"],["configure","configured"],["adjust","adjusted"],["align","aligned"],["normalize","normalized"],["standardize","standardized"],["format","formatted"],["clean","cleaned"],["reset","reset"],["sync","synced"],["init","initialized"],["install","installed"],["skip","skipped"],["resolve","resolved"],["prevent","prevented"],["route","routed"],["defer","deferred"],["surface","surfaced"],["drop","dropped"],["avoid","avoided"],["switch","switched"],["abort","aborted"],["stop","stopped"],["start","started"],["resume","resumed"],["retry","retried"],["expose","exposed"],["strip","stripped"],["scope","scoped"],["check","checked"],["pass","passed"],["ignore","ignored"],["force","forced"],["load","loaded"],["allow","allowed"],["ensure","ensured"],["track","tracked"],["cap","capped"],["return","returned"],["convert","converted"],["verify","verified"],["validate","validated"],["create","created"],["filter","filtered"],["enforce","enforced"],["integrate","integrated"],["render","rendered"],["inject","injected"],["register","registered"],["parse","parsed"],["clear","cleared"],["wrap","wrapped"],["prune","pruned"],["lower","lowered"],["map","mapped"],["populate","populated"],["scrub","scrubbed"],["style","styled"],["truncate","truncated"],["detect","detected"],["apply","applied"],["prefer","preferred"],["discover","discovered"],["evict","evicted"],["structure","structured"],["shorten","shortened"],["annotate","annotated"],["display","displayed"],["transfer","transferred"],["close","closed"],["reorder","reordered"],["rebuild","rebuilt"],["rewrite","rewrote"],["rerun","reran"],["clarify","clarified"],["restore","restored"],["make","made"],["build","built"],["write","wrote"],["run","ran"],["instrument","instrumented"],["regulate","regulated"],["demote","demoted"],["promote","promoted"],["elevate","elevated"],["expand","expanded"],["extend","extended"],["compress","compressed"],["transpile","transpiled"],["decorate","decorated"],["dampen","dampened"],["coerce","coerced"],["collide","collided"],["position","positioned"],["pad","padded"],["pipe","piped"],["instantiate","instantiated"],["group","grouped"],["gather","gathered"],["fail","failed"],["exceed","exceeded"],["invert","inverted"],["bump","bumped"],["use","used"],["preserve","preserved"],["handle","handled"],["support","supported"],["keep","kept"],["show","showed"],["export","exported"],["import","imported"],["read","read"],["set","set"],["put","put"],["split","split"],["spread","spread"],["cut","cut"],["hit","hit"],["hurt","hurt"],["shut","shut"],["let","let"],["bet","bet"],["cast","cast"],["cost","cost"],["quit","quit"],["undo","undid"],["freeze","froze"],["steal","stole"],["stick","stuck"],["strike","struck"],["swing","swung"],["tear","tore"],["throw","threw"],["wake","woke"],["wear","wore"],["weave","wove"],["weep","wept"],["wind","wound"],["win","won"],["withdraw","withdrew"],["breed","bred"],["bring","brought"],["buy","bought"],["catch","caught"],["choose","chose"],["deal","dealt"],["dig","dug"],["feed","fed"],["flee","fled"],["fling","flung"],["fly","flew"],["grow","grew"],["hang","hung"],["lead","led"],["lend","lent"],["light","lit"],["pay","paid"],["ring","rang"],["rise","rose"],["shake","shook"],["sling","slung"],["speak","spoke"],["spring","sprang"],["sting","stung"],["stink","stank"],["swear","swore"],["take","took"],["give","gave"],["find","found"],["hold","held"],["tell","told"],["sell","sold"],["stand","stood"],["understand","understood"],["become","became"],["begin","began"],["fight","fought"],["seek","sought"],["come","came"],["do","did"],["get","got"],["have","had"],["know","knew"],["meet","met"],["see","saw"],["say","said"],["sit","sat"],["beat","beat"],["bend","bent"],["blow","blew"],["cling","clung"],["creep","crept"],["arise","arose"],["override","overrode"],["shrink","shrank"],["sleep","slept"],["slide","slid"],["sweep","swept"],["teach","taught"],["think","thought"],["patch","patched"],["tweak","tweaked"],["refine","refined"],["polish","polished"],["streamline","streamlined"],["decouple","decoupled"],["encapsulate","encapsulated"],["modularize","modularized"],["generalize","generalized"],["specialize","specialized"],["parameterize","parameterized"],["serialize","serialized"],["deserialize","deserialized"],["cache","cached"],["memoize","memoized"],["batch","batched"],["throttle","throttled"],["debounce","debounced"],["paginate","paginated"],["sort","sorted"],["deduplicate","deduplicated"],["flatten","flattened"],["nest","nested"],["rebase","rebased"],["squash","squashed"],["stash","stashed"],["tag","tagged"],["label","labeled"],["comment","commented"],["uncomment","uncommented"],["lint","linted"],["vendor","vendored"],["pin","pinned"],["unpin","unpinned"],["lock","locked"],["downgrade","downgraded"],["upgrade","upgraded"],["backport","backported"],["scaffold","scaffolded"],["bootstrap","bootstrapped"],["provision","provisioned"],["deploy","deployed"],["redeploy","redeployed"],["ship","shipped"],["publish","published"],["unpublish","unpublished"],["draft","drafted"],["finalize","finalized"],["stabilize","stabilized"],["retire","retired"],["archive","archived"],["recover","recovered"],["repair","repaired"],["mock","mocked"],["stub","stubbed"],["benchmark","benchmarked"],["profile","profiled"],["trace","traced"],["log","logged"],["debug","debugged"],["dump","dumped"],["print","printed"],["emit","emitted"],["subscribe","subscribed"],["unsubscribe","unsubscribed"],["notify","notified"],["alert","alerted"],["warn","warned"],["raise","raised"],["panic","panicked"],["swallow","swallowed"],["propagate","propagated"],["connect","connected"],["disconnect","disconnected"],["reconnect","reconnected"],["listen","listened"],["accept","accepted"],["request","requested"],["respond","responded"],["redirect","redirected"],["proxy","proxied"],["forward","forwarded"],["relay","relayed"],["stream","streamed"],["buffer","buffered"],["flush","flushed"],["drain","drained"],["queue","queued"],["dequeue","dequeued"],["enqueue","enqueued"],["poll","polled"],["push","pushed"],["pop","popped"],["peek","peeked"],["fetch","fetched"],["pull","pulled"],["receive","received"],["transmit","transmitted"],["encode","encoded"],["decode","decoded"],["encrypt","encrypted"],["decrypt","decrypted"],["hash","hashed"],["sign","signed"],["authenticate","authenticated"],["authorize","authorized"],["insert","inserted"],["upsert","upserted"],["query","queried"],["index","indexed"],["reindex","reindexed"],["join","joined"],["aggregate","aggregated"],["reduce","reduced"],["fold","folded"],["accumulate","accumulated"],["count","counted"],["sum","summed"],["average","averaged"],["compute","computed"],["calculate","calculated"],["derive","derived"],["infer","inferred"],["deduce","deduced"],["reconcile","reconciled"],["diff","diffed"],["compare","compared"],["match","matched"],["locate","located"],["scan","scanned"],["traverse","traversed"],["walk","walked"],["iterate","iterated"],["loop","looped"],["recurse","recursed"],["spawn","spawned"],["fork","forked"],["kill","killed"],["terminate","terminated"],["halt","halted"],["suspend","suspended"],["pause","paused"],["schedule","scheduled"],["dispatch","dispatched"],["delegate","delegated"],["await","awaited"],["unblock","unblocked"],["yield","yielded"],["detach","detached"],["attach","attached"],["mount","mounted"],["unmount","unmounted"],["remount","remounted"],["unregister","unregistered"],["deregister","deregistered"],["reveal","revealed"],["toggle","toggled"],["focus","focused"],["blur","blurred"],["scroll","scrolled"],["zoom","zoomed"],["drag","dragged"],["click","clicked"],["hover","hovered"],["swipe","swiped"],["animate","animated"],["transition","transitioned"],["fade","faded"],["highlight","highlighted"],["underline","underlined"],["color","colored"],["paint","painted"],["compile","compiled"],["link","linked"],["assemble","assembled"],["package","packaged"],["bundle","bundled"],["minify","minified"],["gate","gated"],["flag","flagged"],["version","versioned"],["namespace","namespaced"],["alias","aliased"],["relabel","relabeled"],["summarize","summarized"],["describe","described"],["explain","explained"],["illustrate","illustrated"],["demonstrate","demonstrated"],["trim","trimmed"],["fill","filled"],["seed","seeded"],["allocate","allocated"],["deallocate","deallocated"],["reserve","reserved"],["free","freed"],["dispose","disposed"],["recycle","recycled"],["reuse","reused"],["share","shared"],["clone","cloned"],["copy","copied"],["duplicate","duplicated"],["replicate","replicated"],["mirror","mirrored"],["snapshot","snapshotted"],["require","required"],["constrain","constrained"],["restrict","restricted"],["limit","limited"],["sanitize","sanitized"],["escape","escaped"],["unescape","unescaped"],["quote","quoted"],["unquote","unquoted"],["whitelist","whitelisted"],["blacklist","blacklisted"],["allowlist","allowlisted"],["denylist","denylisted"],["embed","embedded"],["shred","shredded"],["need","needed"],["speed","sped"],["proceed","proceeded"],["succeed","succeeded"],["heed","heeded"],["download","downloaded"],["upload","uploaded"],["overload","overloaded"],["reload","reloaded"],["initialize","initialized"],["capture","captured"],["release","released"],["wire","wired"],["rewire","rewired"],["head","headed"],["thread","threaded"],["flood","flooded"],["cloud","clouded"],["bleed","bled"],["trigger","triggered"],["silence","silenced"],["mute","muted"],["unmute","unmuted"],["rotate","rotated"],["expire","expired"],["invalidate","invalidated"],["refresh","refreshed"],["warm","warmed"],["prefetch","prefetched"],["prewarm","prewarmed"],["backfill","backfilled"],["checkpoint","checkpointed"],["replay","replayed"],["record","recorded"],["sample","sampled"],["measure","measured"],["meter","metered"],["audit","audited"],["monitor","monitored"],["observe","observed"],["watch","watched"],["inspect","inspected"],["assert","asserted"],["expect","expected"],["cover","covered"],["exercise","exercised"],["stress","stressed"],["fuzz","fuzzed"],["typecheck","typechecked"],["vet","vetted"],["hide","hid"],["draw","drew"],["bear","bore"],["lay","laid"],["leave","left"],["feel","felt"],["mean","meant"],["send","sent"],["spend","spent"],["lose","lost"],["grind","ground"],["slay","slew"],["shoot","shot"],["spin","spun"],["sink","sank"],["drink","drank"],["swim","swam"],["sing","sang"],["forget","forgot"],["forgive","forgave"],["mistake","mistook"],["overcome","overcame"],["redo","redid"],["remake","remade"],["retake","retook"],["foresee","foresaw"],["withhold","withheld"],["uphold","upheld"],["strive","strove"],["awake","awoke"],["bite","bit"],["ride","rode"],["drive","drove"],["dive","dove"],["fall","fell"],["break","broke"],["string","strung"],["wring","wrung"],["hear","heard"],["shine","shone"]],"irregular_past":["left","felt","meant","sent","spent","lost","slept","slid","swept","ground","slew","stank"],"ed_blocklist":["hundred","thousand","red","bed","wed","shed","feed","need","seed","speed","breed","bleed","exceed","proceed","succeed","heed","weed","indeed","deed","greed","creed","steed","reed","embed","shred","sled","hatred","kindred","naked","wicked","sacred","rugged","ragged","jagged","crooked"],"d_blocklist":["and","bad","bid","god","had","kid","lad","mad","mid","mud","nod","odd","old","pad","raid","said","sad","should","would","could","void","valid","solid","rapid","vivid","timid","lucid","acid","fluid","druid","afraid","abroad","instead","ahead","aboard","payload","android","hybrid","liquid","candid","splendid","good","food","mood","wood","hood","blood","brood","dead","bead","loud","proud","aloud","bread","avoid","lead","head","thread","download","upload","overload","reload","flood","cloud","load"],"code_extensions":["rs","c","cpp","cc","cxx","h","hpp","hxx","zig","nim","v","java","kt","kts","scala","groovy","clj","cljs","cs","fs","vb","js","ts","jsx","tsx","mjs","cjs","vue","svelte","astro","py","pyx","pxd","pyi","rb","rake","gemspec","php","go","swift","m","mm","lua","sh","bash","zsh","fish","ps1","psm1","bat","cmd","pl","pm","hs","lhs","ml","mli","elm","ex","exs","erl","hrl","gleam","lisp","cl","el","scm","rkt","jl","r","dart","cr","d","f","f90","f95","f03","f08","ada","adb","ads","cob","cbl","asm","s","sql","plsql","pro","re","rei","nix","tf","hcl","sol","move","cairo","wasm","wat","odin","jai","hare","roc","zir"],"doc_extensions":["md","mdx","markdown","adoc","asciidoc","rst","txt","org","tex","pod","rmd","wiki","textile","texi","texinfo","man","rdoc"],"filler_words":["comprehensive","better","various","several","numerous","powerful","seamless","robust","flexible","versatile","sophisticated","holistic","myriad","cutting-edge","state-of-the-art","world-class","best-in-class"],"meta_phrases":["this commit","this change","this pr","this patch","updated code","updated the","modified code","changed code","improved code","modified the","changed the","made changes","some changes","minor changes","misc changes","various changes","general changes","code changes","refactored code","added code","removed code"],"body_present_tense":["adds","fixes","updates","removes","changes","creates","refactors","implements","migrates","renames","moves","replaces","improves","merges","splits","extracts","restructures","reorganizes","consolidates","deletes","introduces","deprecates","corrects","enhances","reverts","optimizes","simplifies","documents","configures","enables","disables","resolves","prevents","handles","supports","exposes","validates","verifies","converts","parses","renders","registers","filters","enforces","integrates","wraps","returns","uses"]}