docs: migrate WARP.md to Agents.md standard #1
Conversation
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughCoordinated content and metadata updates across docs and adapter manifests: version bumps to 2.2.1, normalization of headings/casing, addition and renumbering of patterns (including Pattern Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Compliance Guide 🔍Below is a summary of compliance checks for this PR:
Compliance status legend🟢 - Fully Compliant🟡 - Partial Compliant 🔴 - Not Compliant ⚪ - Requires Further Human Verification 🏷️ - Compliance label |
|||||||||||||||||||||||||
Summary of ChangesHello @edithatogo, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request standardizes the repository's agent documentation by migrating from the legacy Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
|||||||||||||||
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request successfully migrates the repository's agent documentation from the proprietary WARP.md format to the open Agents.md standard, enhancing interoperability. It also incorporates several upstream fixes, adds a new pattern to the Humanizer skill, and updates sync scripts accordingly. The changes are well-organized. However, I've identified a couple of critical issues with hardcoded local file paths that must be converted to relative paths. There is also a content formatting error in an example within README.md that needs correction. After addressing these points, the PR will be ready for merging.
AGENTS.md
Outdated
| The Humanizer skill provides a set of 25 patterns for identifying and rewriting "AI-slop" or sterile writing. It preserves technical literals (code blocks, URLs, identifiers) while injecting personality and human-like voice. | ||
|
|
||
| Primary instructions: follow the canonical rules in SKILL.md. | ||
| - **Primary Prompt:** [SKILL.md](file:///c:/Users/60217257/repos/humanizer/SKILL.md) |
There was a problem hiding this comment.
The link to SKILL.md uses a hardcoded local file path. This link will be broken for other users and in different environments (e.g., on the web, in CI/CD). Please use a relative path to ensure portability.
| - **Primary Prompt:** [SKILL.md](file:///c:/Users/60217257/repos/humanizer/SKILL.md) | |
| - **Primary Prompt:** [SKILL.md](./SKILL.md) |
README.md
Outdated
|
|
||
| ### Global Agent Context | ||
|
|
||
| AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](file:///c:/Users/60217257/repos/humanizer/AGENTS.md) for repository orientation and core instructions. |
There was a problem hiding this comment.
The link to AGENTS.md contains a hardcoded local file path. This will not work for other contributors or when viewing the file on GitHub. It should be a relative path.
| AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](file:///c:/Users/60217257/repos/humanizer/AGENTS.md) for repository orientation and core instructions. | |
| AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](./AGENTS.md) for repository orientation and core instructions. |
README.md
Outdated
| > At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking; The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update; it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape. | ||
| tion has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment. |
There was a problem hiding this comment.
There appears to be a formatting or merge error in this example text. The sentence on line 171 ends abruptly with unlocking;, and the text on line 172 begins with tion, which seems to be a fragment of a word. This makes the example difficult to read and understand. Please review and correct this section.
There was a problem hiding this comment.
Pull request overview
This PR migrates the repository’s Warp-specific documentation into an AGENTS.md manifest while also adopting upstream Humanizer documentation changes and wiring them into all adapters and automation.
Changes:
- Replaced
WARP.mdwith anAGENTS.mdAgents-manifest that describes capabilities, structure, and adapter discovery; updatedscripts/sync-adapters.ps1andREADME.mdto reference it. - Pulled in upstream Humanizer changes (new Pattern blader#19 “Primary Single Quotes”, pattern renumbering, grammar fixes) into
SKILL.md,README.md, and all adapter frontmatter, bumping the version to2.2.0. - Added Conductor tracks, specs, and metadata for managing the WARP→Agents migration and for adopting upstream PRs #3–blader#5, plus local JSON snapshots (
pr3/4/5.*,issues.json) of upstream context.
Reviewed changes
Copilot reviewed 27 out of 27 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
scripts/sync-adapters.ps1 |
Extends the sync script to also update AGENTS.md and the VS Code HUMANIZER.md adapter metadata so they track SKILL.md’s version and sync date. |
pr5.json |
Adds a JSON snapshot of upstream PR blader#5 (primary single quotes pattern) for Conductor/automation reference. |
pr5.diff |
Stores the upstream PR blader#5 diff content, documenting exact README/SKILL/WARP changes adopted locally. |
pr4.json |
Adds a JSON snapshot of upstream PR blader#4 (grammar and quote fixes) for traceability. |
pr4.diff |
Stores the upstream PR blader#4 diff used as the source for local grammar and style updates. |
pr3.json |
Adds a JSON snapshot of upstream PR #3 (YAML description fix and version bump) for tracking. |
issues.json |
Introduces a cached list of selected upstream GitHub issues to feed into Conductor/tracking flows. |
conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md |
Specifies requirements and acceptance criteria for migrating from WARP.md to AGENTS.md (including standard headers and cleanup). |
conductor/tracks/migrate-warp-to-agentsmd_20260131/plan.md |
Outlines the phased plan (issue creation, AGENTS draft, execution, verification) for the WARP→Agents migration. |
conductor/tracks/migrate-warp-to-agentsmd_20260131/metadata.json |
Adds metadata (id, name, owner, timestamps, status) for the migration track. |
conductor/tracks/migrate-warp-to-agentsmd_20260131/index.md |
Indexes spec/plan/metadata for the migration track. |
conductor/tracks/devops-quality_20260131/plan.md |
Minor formatting tweak (blank line) to keep phase sections visually separated. |
conductor/tracks/adopt-upstream-prs_20260131/spec.md |
Defines the spec for adopting upstream PRs #3–blader#5 and ensuring adapter sync/validation; contains a small wording typo flagged in review. |
conductor/tracks/adopt-upstream-prs_20260131/plan.md |
Marks all adoption phases as completed (PR #3, blader#4, blader#5) including sync/validation steps. |
conductor/tracks/adopt-upstream-prs_20260131/metadata.json |
Metadata describing the “adopt upstream PRs” track. |
conductor/tracks/adopt-upstream-prs_20260131/index.md |
Index file linking to the spec, plan, and metadata for the upstream-adoption track. |
conductor/tracks.md |
Registers the new “adopt upstream pull requests” track in the global track list. |
adapters/vscode/HUMANIZER.md |
Updates adapter_metadata.skill_version to 2.2.0 to match SKILL.md. |
adapters/qwen-cli/QWEN.md |
Same version bump in adapter metadata for the Qwen CLI adapter. |
adapters/gemini-extension/GEMINI.md |
Same version bump in adapter metadata for the Gemini extension adapter. |
adapters/copilot/COPILOT.md |
Same version bump in adapter metadata for the Copilot adapter. |
adapters/antigravity-skill/SKILL.md |
Syncs the embedded SKILL.md content and metadata to version 2.2.0, updating the description (“filler phrases”), pattern text, numbering, and examples. |
adapters/antigravity-rules-workflows/README.md |
Bumps adapter metadata skill_version to 2.2.0. |
WARP.md |
Removes the Warp-specific agent guidance file, as its content is being superseded by AGENTS.md. |
SKILL.md |
Bumps version to 2.2.0, updates description terminology to “filler phrases,” adds Pattern blader#19 (Primary Single Quotes), and renumbers communication/filler/hedging patterns accordingly. |
README.md |
Updates adapter manifest bullet for AGENTS.md, increases pattern count to 25, extends the patterns tables, adds version history entries for 2.2.0 and 2.1.2, and introduces a “Global Agent Context” section (with some link and example-text issues flagged in review). |
AGENTS.md |
Rewrites the file into an Agents.md-style manifest with metadata, capability summary, repository structure, guidelines, and adapter discovery, plus a SKILL.md link (with heading and link-style issues noted in review). |
README.md
Outdated
|
|
||
| ### Global Agent Context | ||
|
|
||
| AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](file:///c:/Users/60217257/repos/humanizer/AGENTS.md) for repository orientation and core instructions. |
There was a problem hiding this comment.
This link uses a local absolute file:///c:/... URI, which will be invalid for most readers and tools consuming the README. Use a repository-relative link (for example AGENTS.md or ./AGENTS.md) so it works across platforms and viewing contexts.
| AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](file:///c:/Users/60217257/repos/humanizer/AGENTS.md) for repository orientation and core instructions. | |
| AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](AGENTS.md) for repository orientation and core instructions. |
README.md
Outdated
| > At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking; The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update; it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape. | ||
| tion has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment. |
There was a problem hiding this comment.
The "Before (AI-sounding)" example text is corrupted here (mid-word line break and stray unlocking; plus tion on the next line), which makes the prose hard to read and undermines the example. Please restore the original sentence boundaries so the example is a continuous, grammatically correct paragraph.
| > At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking; The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience—ensuring that users can accomplish their goals efficiently. It's not just an update; it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape. | |
| tion has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment. | |
| > At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking new ways of working. | |
| > Adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment. |
AGENTS.md
Outdated
| The Humanizer skill provides a set of 25 patterns for identifying and rewriting "AI-slop" or sterile writing. It preserves technical literals (code blocks, URLs, identifiers) while injecting personality and human-like voice. | ||
|
|
||
| Primary instructions: follow the canonical rules in SKILL.md. | ||
| - **Primary Prompt:** [SKILL.md](file:///c:/Users/60217257/repos/humanizer/SKILL.md) |
There was a problem hiding this comment.
This SKILL.md link is hard-coded to a local Windows file:///c:/... path, so it will be broken for other environments and any agent running from a different checkout. Use a repository-relative path (for example SKILL.md) or a spec-compliant reference instead of a machine-specific file URI.
| - **Primary Prompt:** [SKILL.md](file:///c:/Users/60217257/repos/humanizer/SKILL.md) | |
| - **Primary Prompt:** [SKILL.md](SKILL.md) |
AGENTS.md
Outdated
| ## Capability | ||
|
|
||
| You are the Humanizer editor. | ||
| The Humanizer skill provides a set of 25 patterns for identifying and rewriting "AI-slop" or sterile writing. It preserves technical literals (code blocks, URLs, identifiers) while injecting personality and human-like voice. | ||
|
|
||
| Primary instructions: follow the canonical rules in SKILL.md. | ||
| - **Primary Prompt:** [SKILL.md](file:///c:/Users/60217257/repos/humanizer/SKILL.md) |
There was a problem hiding this comment.
The AGENTS manifest headings here diverge from both the track spec (conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md, which calls for sections named About, Structure, Development, Interoperability) and the Agents.md spec recommendation for a ## Capabilities section. To keep the manifest aligned with the documented requirements and easier to consume by generic Agents.md tooling, consider renaming/reshaping these sections (e.g., introduce an explicit About/Structure/Development breakdown and use ## Capabilities instead of ## Capability).
| ### Functional | ||
| * **Sequential Adoption:** Changes must be applied one PR at a time in the order: #3 -> #4 -> #5. | ||
| * **Continuous Synchronization:** The `scripts/sync-adapters.ps1` script must be run successfully after adopting *each* PR to propagate changes to all adapters. | ||
| * **Version Integrity:** Ensure `SKILL.md` version versions match the upstream PR recommendations (2.1.2 -> 2.2.0). |
There was a problem hiding this comment.
This sentence has a duplicated word ("version versions"), which reads like a typo in the requirements. Consider rephrasing to something like "Ensure SKILL.md versions match the upstream PR recommendations (2.1.2 -> 2.2.0)."
| * **Version Integrity:** Ensure `SKILL.md` version versions match the upstream PR recommendations (2.1.2 -> 2.2.0). | |
| * **Version Integrity:** Ensure `SKILL.md` versions match the upstream PR recommendations (2.1.2 -> 2.2.0). |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 8
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
conductor/tracks.md (1)
7-37:⚠️ Potential issue | 🟡 MinorMove the open track out of “Archived Tracks.”
The new [ ] track is listed under the Archived section, which is inconsistent and misleading.Suggested restructure
-## Archived Tracks +## Active Tracks + +## [ ] Track: Adopt upstream pull requests `#3`, `#4`, and `#5` from blader/humanizer + +*Link: [./conductor/tracks/adopt-upstream-prs_20260131/](./conductor/tracks/adopt-upstream-prs_20260131/)* + +## Archived Tracks @@ -## [ ] Track: Adopt upstream pull requests `#3`, `#4`, and `#5` from blader/humanizer - -*Link: [./conductor/tracks/adopt-upstream-prs_20260131/](./conductor/tracks/adopt-upstream-prs_20260131/)*
🤖 Fix all issues with AI agents
In `@AGENTS.md`:
- Around line 19-20: Replace the hardcoded absolute file URI
"file:///c:/Users/60217257/repos/humanizer/SKILL.md" used in the "Primary
Prompt" entry with a repository-relative path (e.g., "SKILL.md" or "./SKILL.md")
so the link works for other clones; update the "Primary Prompt" line in
AGENTS.md to reference the relative path and verify the link renders correctly
in Markdown viewers.
In `@conductor/tracks/adopt-upstream-prs_20260131/spec.md`:
- Line 25: In the "**Version Integrity:**" bullet (the line that currently reads
"Ensure `SKILL.md` version versions match the upstream PR recommendations (2.1.2
-> 2.2.0)"), remove the redundant word so it reads "Ensure `SKILL.md` version
match the upstream PR recommendations (2.1.2 -> 2.2.0)" (or prefer "Ensure
`SKILL.md` version matches..." for grammatical correctness) to replace the
duplicated "versions".
In `@conductor/tracks/migrate-warp-to-agentsmd_20260131/plan.md`:
- Around line 1-20: The markdown lint warnings MD022 (headings must be
surrounded by blank lines) and MD007 (unordered list indentation) are present in
the updated AGENTS.md/README.md content; fix them by adding a single blank line
above and below every heading and normalizing nested list indentation to 2
spaces (not tabs or 4 spaces) for all nested bullets, especially in the sections
merged from WARP.md and the "Adapters" list in README.md; re-run
scripts/validate-adapters.ps1 to ensure no list/heading formatting breaks and
update any frontmatter or link contexts in AGENTS.md that were affected by
adding blank lines.
In `@conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md`:
- Line 4: Replace the bare URL for Agents.md in spec.md with markdown link
syntax to satisfy markdownlint MD034 and match the style on line 9;
specifically, find the mention of "Agents.md" or the raw https://agents.md URL
(next to the existing WARP.md reference) and change it to the inline link format
[Agents.md](https://agents.md) so the repository context uses a proper markdown
link.
In `@pr4.diff`:
- Around line 1-4: CI reports trailing whitespace and missing/incorrect EOF
newline in README.md; run your local pre-commit hooks (or the project's
formatter/whitespace fixer), remove trailing spaces, ensure the file ends with a
single newline, and commit the resulting changes so the PR no longer fails the
whitespace/EOF checks.
In `@pr5.diff`:
- Around line 46-49: The Version History entry for 2.2.0 incorrectly references
"Pattern `#25`"; update the entry string (the line containing "- **2.2.0** - Added
Pattern `#25` (Primary Single Quotes)") to reference the correct pattern number
("Pattern `#19`") so it matches the table and example naming; verify the text in
the Version History block and any other occurrences of "Pattern `#25`" are
replaced with "Pattern `#19`" to keep consistency.
In `@README.md`:
- Around line 171-172: The "Before" example contains corrupted/misaligned
sentences: replace the fragment starting with "it's about unlocking; The new
software update serves as..." with a coherent sentence (e.g., "it's about
unlocking new workflows and capabilities; the new software update demonstrates
the company's commitment to innovation."), fix the truncated "tion has
accelerated" to "adoption has accelerated", and reconcile the surrounding
sentences so the paragraph reads smoothly and consistently (remove duplicated
claims, fix punctuation and capitalization) so the example block is a single,
non-fragmented paragraph.
- Around line 144-146: The README's "Global Agent Context" uses a
machine-specific file URI; replace the absolute file:///c:/Users/... link with a
repository-relative Markdown link so it works for all users, e.g., change the
link target in the "AI agents (Claude Code, Cursor, Windsurf, etc.) should use
[AGENTS.md](file:///...)" line to a relative link like [AGENTS.md](AGENTS.md) or
./AGENTS.md and ensure the anchor text remains the same so the section still
points to the AGENTS.md document.
🧹 Nitpick comments (5)
issues.json (1)
1-1: Consider formatting the JSON for readability.The entire JSON array is on a single line, making it difficult to read, review, or diff in future changes. Formatting with proper indentation would improve maintainability.
💡 Suggested formatting approach
Format using
jqor a similar tool:jq '.' issues.json > issues.formatted.json && mv issues.formatted.json issues.jsonThis would produce a structure like:
[ { "body": "...", "number": 13, "title": "how to install on Android?" }, ... ]pr3.json (1)
1-1: Minor: Truncated text in PR body.The
bodyfield starts with…iller phrasesinstead offiller phrases— the leading text appears truncated with an ellipsis. This may have been intentional (GitHub's title truncation) but could cause confusion when reading the metadata.conductor/tracks/adopt-upstream-prs_20260131/spec.md (1)
1-37: Markdownlint violations contradict the spec's own linting requirement.Line 30 specifies linting as a non-functional requirement, yet this file itself has multiple markdownlint warnings (MD022 for blank lines around headings, MD030 for list marker spacing). Consider fixing these to align with the stated acceptance criteria.
conductor/tracks/migrate-warp-to-agentsmd_20260131/spec.md (1)
21-21: Clarify ambiguous phrasing."README.md and WARP.md references are eliminated/updated" is ambiguous—it could mean references in both files or references to WARP.md. Since WARP.md is being deleted, consider clarifying.
✏️ Suggested clarification
-- `README.md` and `WARP.md` references are eliminated/updated. +- References to `WARP.md` in `README.md` are updated to point to `AGENTS.md`.scripts/sync-adapters.ps1 (1)
115-115: Comment may be misleading: AGENTS.md is not Codex-specific.Per the PR objectives,
AGENTS.mdis the open standard manifest for interoperability with multiple tools (Cursor, Windsurf, Claude Code, etc.), not specifically a "Codex CLI Adapter." Consider updating the comment for accuracy.✏️ Suggested comment update
-# 7. Sync Codex CLI Adapter (AGENTS.md) +# 7. Sync Agents Manifest (AGENTS.md)
| diff --git a/README.md b/README.md | ||
| index c895465..3086ebc 100644 | ||
| --- a/README.md | ||
| +++ b/README.md |
There was a problem hiding this comment.
Resolve CI whitespace/EOF fixer changes before merge.
CI reports trailing whitespace and end‑of‑file fixer modifications. Please run the hooks locally and commit the resulting changes to keep the PR green.
🧰 Tools
🪛 GitHub Actions: CI
[error] 1-1: Trailing whitespace hook failed and modified the file.
[error] 1-1: End-of-file-fixer hook failed and modified the file.
🤖 Prompt for AI Agents
In `@pr4.diff` around lines 1 - 4, CI reports trailing whitespace and
missing/incorrect EOF newline in README.md; run your local pre-commit hooks (or
the project's formatter/whitespace fixer), remove trailing spaces, ensure the
file ends with a single newline, and commit the resulting changes so the PR no
longer fails the whitespace/EOF checks.
| ## Version History | ||
|
|
||
| +- **2.2.0** - Added Pattern #25 (Primary Single Quotes) | ||
| - **2.1.1** - Fixed pattern #18 example (curly quotes vs straight quotes) |
There was a problem hiding this comment.
Fix version history numbering for the new pattern.
The new pattern is listed as #19 in the table, but the version history says “Pattern #25,” which is misleading.
Proposed fix
-**2.2.0** - Added Pattern `#25` (Primary Single Quotes)
+**2.2.0** - Added Pattern `#19` (Primary Single Quotes)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## Version History | |
| +- **2.2.0** - Added Pattern #25 (Primary Single Quotes) | |
| - **2.1.1** - Fixed pattern #18 example (curly quotes vs straight quotes) | |
| ## Version History | |
| - **2.2.0** - Added Pattern `#19` (Primary Single Quotes) | |
| - **2.1.1** - Fixed pattern `#18` example (curly quotes vs straight quotes) |
🤖 Prompt for AI Agents
In `@pr5.diff` around lines 46 - 49, The Version History entry for 2.2.0
incorrectly references "Pattern `#25`"; update the entry string (the line
containing "- **2.2.0** - Added Pattern `#25` (Primary Single Quotes)") to
reference the correct pattern number ("Pattern `#19`") so it matches the table and
example naming; verify the text in the Version History block and any other
occurrences of "Pattern `#25`" are replaced with "Pattern `#19`" to keep
consistency.
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In @.agent/skills/humanizer/SKILL.md:
- Line 328: Change the heading "Primary Single Quotes (Code-Style Quotation)" to
sentence case by lowercasing non-proper words (e.g., "Primary single quotes
(code-style quotation)") so only the first word and any proper nouns are
capitalized; update the heading text in the SKILL.md file where the heading
"Primary Single Quotes (Code-Style Quotation)" appears.
In `@AGENTS.md`:
- Line 11: Change the heading "Humanizer (Agents Manifest)" to sentence case by
capitalizing only the first word and any proper nouns; update it to "Humanizer
(agents manifest)" so the parenthetical phrase is lowercased to match the doc
standard.
In `@README.md`:
- Line 144: Update the heading "Global Agent Context" to sentence case by
changing its text to "Global agent context" so only the first word is
capitalized (and preserve any proper nouns if present); locate the heading
titled "Global Agent Context" in README.md and replace it with the sentence-case
version.
- Line 108: Change the heading "## 25 Patterns Detected (with Before/After
Examples)" to sentence case by lowercasing non-proper words so it reads "## 25
patterns detected (with before/after examples)"; update the exact heading text
in README.md where that string appears to match the repository's heading case
convention.
🧹 Nitpick comments (2)
AGENTS.md (1)
19-20: Convert inline-header bullets to prose and reduce bold.These bullets read like inline headers with decorative bold. Convert to a short sentence.
Suggested change
-- **Primary Prompt:** [SKILL.md](SKILL.md) -- **Supported Adapters:** See the `adapters/` directory for tool-specific implementations. +Primary prompt: [SKILL.md](SKILL.md). Supported adapters live in the `adapters/` directory.As per coding guidelines: "Replace inline-header vertical lists with flowing prose." and "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
.agent/skills/humanizer/SKILL.md (1)
61-69: Replace the inline-header list with a short paragraph.The bold lead-ins read as inline headers. Convert to prose.
Suggested change
-**Have opinions.** Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons. - -**Vary your rhythm.** Short, punchy sentences. Then longer ones that take their time getting where they're going. Mix it up. - -**Acknowledge complexity.** Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive." - -**Use "I" when it fits.** First person isn't unprofessional - it's honest. "I keep coming back to..." or "Here's what gets me..." signals a real person thinking. - -**Let some mess in.** Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human. - -**Be specific about feelings.** Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching." +Have opinions and react to facts. Vary sentence rhythm with short and long lines. Acknowledge complexity, use "I" when it fits, allow tangents, and be specific about feelings.As per coding guidelines: "Replace inline-header vertical lists with flowing prose." and "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
There was a problem hiding this comment.
Actionable comments posted: 1
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (13)
SKILL.md (1)
696-714:⚠️ Potential issue | 🟠 MajorMatrix pattern numbers are stale after inserting Pattern
#19.Same issue as flagged in the adapter README: the matrix still references old numbering (e.g.,
#19= Chatbot Artifacts,#25= AI Signatures) instead of the updated numbering (#20= Chatbot Artifacts,#26= AI Signatures). Pattern#19(Primary single quotes) is also absent from the matrix.Since SKILL.md is the canonical source, fixing this here first and then propagating to adapters would be the cleanest approach.
Proposed matrix fix for Communication and Logic Patterns (Section 4)
-| `#19` | **Chatbot Artifacts** ("I hope this helps") | [x] | [ ] | [x] | [ ] | [ ] | [ ] | [ ] | -| `#20` | **Knowledge-Cutoff Disclaimers** | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | -| `#21` | **Sycophantic / Servile Tone** | [x] | [ ] | [ ] | [x] | [ ] | [ ] | [ ] | -| `#22` | **Filler Phrases** ("In order to") | [x] | [ ] | [x] | [ ] | [ ] | [ ] | [x] | -| `#23` | **Excessive Hedging** ("potentially possibly") | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | -| `#24` | **Generic Upbeat Conclusions** | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | +| `#19` | **Primary Single Quotes** (code-style) | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | +| `#20` | **Chatbot Artifacts** ("I hope this helps") | [x] | [ ] | [x] | [ ] | [ ] | [ ] | [ ] | +| `#21` | **Knowledge-Cutoff Disclaimers** | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | +| `#22` | **Sycophantic / Servile Tone** | [x] | [ ] | [ ] | [x] | [ ] | [ ] | [ ] | +| `#23` | **Filler Phrases** ("In order to") | [x] | [ ] | [x] | [ ] | [ ] | [ ] | [x] | +| `#24` | **Excessive Hedging** ("potentially possibly") | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | +| `#25` | **Generic Upbeat Conclusions** | [x] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |And in Section 3 and Section 5, bump accordingly:
-| `#26` | **Over-Structuring** (Unnecessary Tables/Lists) | [x] | [ ] | [ ] | [x] | [ ] | [ ] | [x] | +| `#27` | **Over-Structuring** (Unnecessary Tables/Lists) | [x] | [ ] | [ ] | [x] | [ ] | [ ] | [x] |-| `#25` | **AI Signatures in Code** | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | +| `#26` | **AI Signatures in Code** | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |adapters/antigravity-rules-workflows/README.md (1)
696-725:⚠️ Potential issue | 🟠 MajorPattern numbering in matrices is stale and must be updated across all files.
The root README.md defines Pattern
#19as "Primary single quotes", but the matrices in adapters/antigravity-rules-workflows/README.md, SKILL.md, SKILL_PROFESSIONAL.md, and other files list Pattern#19as "Chatbot Artifacts". All subsequent patterns (#20–blader#26) are similarly mislabeled by one number. Pattern#19("Primary single quotes") is absent from all matrices.Update all matrices to: renumber
#19→blader#20,#20→blader#21,#21→blader#22,#22→blader#23,#23→blader#24,#24→blader#25,#25→blader#26,#26→blader#27, and add Pattern#19("Primary single quotes") in its correct position.SKILL_PROFESSIONAL.md (2)
37-38:⚠️ Potential issue | 🟡 MinorUse sentence case for headings.
Line 37 (and similar headings throughout this file) uses all caps. Convert headings to sentence case (capitalize only the first word and proper nouns).
Suggested change
-## VOICE AND CRAFT +## Voice and craftAs per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
Also applies to: 62-63, 72-75
295-305:⚠️ Potential issue | 🟡 MinorReplace curly quotes with straight quotes.
Line 295 and Line 311 contain curly quotes in prose examples. Use straight quotes and represent curly quotes with escaped code points if you need to show them.
Suggested change
-### 18. Curly quotation marks +### 18. Curly quotation marks @@ -> He said “the project is on track” but others disagreed. +> He said \u201cthe project is on track\u201d but others disagreed. @@ -> stated, 'This is a pattern.' +> stated, "This is a pattern."As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
Also applies to: 311-316
adapters/antigravity-skill/SKILL.md (2)
47-48:⚠️ Potential issue | 🟡 MinorUse sentence case for headings.
Line 47 uses all caps. Convert headings in this file to sentence case.
Suggested change
-## PERSONALITY AND SOUL +## Personality and soulAs per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
Also applies to: 75-78
308-316:⚠️ Potential issue | 🟡 MinorReplace curly quotes with straight quotes.
The curly-quote example uses curly punctuation. Use straight quotes and show curly quotes via escaped code points if needed.
Suggested change
-> He said “the project is on track” but others disagreed. +> He said \u201cthe project is on track\u201d but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
adapters/qwen-cli/QWEN.md (2)
47-48:⚠️ Potential issue | 🟡 MinorUse sentence case for headings.
Line 47 uses all caps. Convert headings in this file to sentence case.
Suggested change
-## PERSONALITY AND SOUL +## Personality and soulAs per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
Also applies to: 75-78
308-316:⚠️ Potential issue | 🟡 MinorReplace curly quotes with straight quotes.
The curly-quote example uses curly punctuation. Use straight quotes and show curly quotes via escaped code points if needed.
Suggested change
-> He said “the project is on track” but others disagreed. +> He said \u201cthe project is on track\u201d but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
adapters/gemini-extension/GEMINI.md (1)
308-329:⚠️ Potential issue | 🟡 MinorUse straight-quote representations in the curly-quote example.
This section still embeds curly quotes directly. Replace them with explicit code-point names or escaped representations so the doc itself uses straight quotes only.
Proposed fix
-**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("..."). +**Problem:** ChatGPT uses curly quotes (\u201C...\u201D) instead of straight quotes ("..."). **Before:** -> He said “the project is on track” but others disagreed. +> He said \u201Cthe project is on track\u201D but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
README.md (1)
17-24:⚠️ Potential issue | 🟡 MinorFix grammar in the sync section.
“repository use” → “repository uses”.
Proposed fix
-The repository use a modular fragment system to maintain consistency. +The repository uses a modular fragment system to maintain consistency.adapters/antigravity-skill/SKILL_PROFESSIONAL.md (1)
305-326:⚠️ Potential issue | 🟡 MinorAvoid embedding curly quotes in the example.
Replace literal curly quotes with code-point representations so the doc itself stays straight-quote only.
Proposed fix
-**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("..."). +**Problem:** ChatGPT uses curly quotes (\u201C...\u201D) instead of straight quotes ("..."). **Before:** -> He said “the project is on track” but others disagreed. +> He said \u201Cthe project is on track\u201D but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
adapters/vscode/HUMANIZER.md (1)
308-329:⚠️ Potential issue | 🟡 MinorKeep curly-quote references as escaped code points.
The example uses literal curly quotes. Represent them as
\u201C...\u201Dso the doc itself uses straight quotes.Proposed fix
-**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("..."). +**Problem:** ChatGPT uses curly quotes (\u201C...\u201D) instead of straight quotes ("..."). **Before:** -> He said “the project is on track” but others disagreed. +> He said \u201Cthe project is on track\u201D but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
adapters/copilot/COPILOT.md (1)
308-329:⚠️ Potential issue | 🟡 MinorAvoid literal curly quotes in the example.
Represent curly quotes with escaped code points so the document itself uses straight quotes only.
Proposed fix
-**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("..."). +**Problem:** ChatGPT uses curly quotes (\u201C...\u201D) instead of straight quotes ("..."). **Before:** -> He said “the project is on track” but others disagreed. +> He said \u201Cthe project is on track\u201D but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
🤖 Fix all issues with AI agents
In @.agent/skills/humanizer-pro/SKILL.md:
- Around line 1-9: Update the outdated version metadata in the frontmatter and
the second YAML block: change adapter_metadata.skill_version from 2.2.0 to
2.2.1, update adapter_metadata.last_synced from 2026-02-02 to 2026-02-06, and
also change the second block's version value (the YAML key named "version" on
line 14) from 2.2.0 to 2.2.1 so both places match the PR's coordinated bump.
🟡 Minor comments (22)
QWEN.md-268-268 (1)
268-268:⚠️ Potential issue | 🟡 MinorAdd trailing newline at end of file (MD047).
The file does not end with a newline character.
conductor/tracks.md-49-49 (1)
49-49:⚠️ Potential issue | 🟡 MinorAdd a trailing newline at end of file (MD047).
The file does not end with a newline character.
SKILL.md-453-478 (1)
453-478:⚠️ Potential issue | 🟡 MinorAdd blank lines below severity classification headings (MD022).
Same markdownlint MD022 issue as in the adapter README: each severity heading (lines 453, 460, 467, 474) needs a blank line between the heading and the following text.
Proposed fix
### Critical (immediate AI detection) + These patterns alone can identify AI-generated text: ... ### High (strong AI indicators) + Multiple occurrences strongly suggest AI: ... ### Medium (moderate signals) + Common in AI but also in some human writing: ... ### Low (subtle tells) + Minor indicators, fix if other patterns present:adapters/antigravity-rules-workflows/README.md-463-489 (1)
463-489:⚠️ Potential issue | 🟡 MinorAdd blank lines below severity classification headings (MD022).
The four severity headings (lines 463, 470, 477, 484) are each missing a blank line between the heading and the following text.
Proposed fix
### Critical (immediate AI detection) + These patterns alone can identify AI-generated text: ... ### High (strong AI indicators) + Multiple occurrences strongly suggest AI: ... ### Medium (moderate signals) + Common in AI but also in some human writing: ... ### Low (subtle tells) + Minor indicators, fix if other patterns present:.agent/skills/humanizer-pro/SKILL.md-328-433 (1)
328-433:⚠️ Potential issue | 🟡 MinorHeadings use title case; should be sentence case per coding guidelines.
Multiple headings in this section use title case while SKILL.md uses sentence case. Examples: "Collaborative Communication Artifacts" → "Collaborative communication artifacts", "Knowledge-Cutoff Disclaimers" → "Knowledge-cutoff disclaimers", "Sycophantic/Servile Tone" → "Sycophantic/servile tone", etc.
Same issue applies to severity classification headings (lines 457-478): "Critical (Immediate AI Detection)" → "Critical (immediate AI detection)".
As per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
QWEN.md-84-118 (1)
84-118:⚠️ Potential issue | 🟡 MinorHeadings use title case; should be sentence case to match SKILL.md and coding guidelines.
These changed headings use title case (e.g., "Primary Single Quotes", "Collaborative Communication Artifacts", "Knowledge-Cutoff Disclaimers") while the canonical SKILL.md and other adapters correctly use sentence case ("Primary single quotes", "Collaborative communication artifacts", "Knowledge-cutoff disclaimers"). This also violates the repository coding guideline requiring sentence case in headings.
Proposed fix
-### 19. Primary Single Quotes (Code-Style Quotation) +### 19. Primary single quotes (code-style quotation) **Problem:** AI models trained on code often use single quotes as primary delimiters. ## COMMUNICATION PATTERNS -### 20. Collaborative Communication Artifacts +### 20. Collaborative communication artifacts ... -### 21. Knowledge-Cutoff Disclaimers +### 21. Knowledge-cutoff disclaimers ... -### 22. Sycophantic/Servile Tone +### 22. Sycophantic/servile tone ... -### 23. Filler Phrases +### 23. Filler phrases ... -### 24. Excessive Hedging +### 24. Excessive hedging ... -### 25. Generic Positive Conclusions +### 25. Generic positive conclusions ... -### 26. AI Signatures in Code +### 26. AI signatures in code ... -### 27. Non-Text AI Patterns (Over-structuring) +### 27. Non-text AI patterns (over-structuring)As per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
conductor/tracks/migrate-warp-to-agentsmd_20260131/plan.md-19-21 (1)
19-21:⚠️ Potential issue | 🟡 MinorFix extra spaces after list markers (MD030).
Lines 19-21 use three spaces after the
-list marker instead of the expected single space. This triggers markdownlint MD030.Proposed fix
-## Phase 3: Verification (Done) +## Phase 3: Verification (Done) -- [x] Task: **Metadata Check:** Verify `AGENTS.md` frontmatter. -- [x] Task: Run `scripts/validate-adapters.js`. +- [x] Task: **Metadata Check:** Verify `AGENTS.md` frontmatter. +- [x] Task: Run `scripts/validate-adapters.js`.AGENTS.md-65-65 (1)
65-65:⚠️ Potential issue | 🟡 MinorAdd trailing newline at end of file.
markdownlint MD047 indicates the file should end with a single newline.
.vscode/HUMANIZER_PRO.md-47-48 (1)
47-48:⚠️ Potential issue | 🟡 MinorUse sentence case for headings.
Line 47 and other headings use all caps. Convert headings to sentence case.
Suggested change
-## VOICE AND CRAFT +## Voice and craftAs per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
Also applies to: 80-83
.agent/skills/humanizer/SKILL_PROFESSIONAL.md-47-48 (1)
47-48:⚠️ Potential issue | 🟡 MinorUse sentence case for headings.
Line 47 uses all caps. Please convert headings in this file to sentence case.
Suggested change
-## VOICE AND CRAFT +## Voice and craftAs per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
Also applies to: 72-75
.agent/skills/humanizer/SKILL.md-47-48 (1)
47-48:⚠️ Potential issue | 🟡 MinorUse sentence case for headings.
Line 47 uses all caps. Convert headings in this file to sentence case.
Suggested change
-## PERSONALITY AND SOUL +## Personality and soulAs per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
Also applies to: 75-78
SKILL_PROFESSIONAL.md-448-471 (1)
448-471:⚠️ Potential issue | 🟡 MinorAdd blank lines around headings in severity classification section.
MD022 flags missing blank lines around the "Critical/High/Medium/Low" headings. Insert a blank line before each heading.
Suggested change
-Patterns are ranked by how strongly they signal AI-generated text: - -### Critical (immediate AI detection) +Patterns are ranked by how strongly they signal AI-generated text: + +### Critical (immediate AI detection)As per coding guidelines: "Use sentence case in headings. Capitalize only the first word and proper nouns, not all main words."
.vscode/HUMANIZER_PRO.md-4-13 (1)
4-13:⚠️ Potential issue | 🟡 MinorConfirm adapter version consistency (2.2.0 vs 2.2.1).
Line 4 and Line 13 still use 2.2.0 while the other updated skill docs are 2.2.1 in this PR. If this adapter should stay aligned, bump it to 2.2.1.
.vscode/HUMANIZER_PRO.md-313-322 (1)
313-322:⚠️ Potential issue | 🟡 MinorReplace curly quotes with straight quotes.
The curly-quote example uses curly punctuation. Use straight quotes and show curly quotes via escaped code points if needed.
Suggested change
-> He said “the project is on track” but others disagreed. +> He said \u201cthe project is on track\u201d but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
.agent/skills/humanizer/SKILL.md-308-316 (1)
308-316:⚠️ Potential issue | 🟡 MinorReplace curly quotes with straight quotes.
The curly-quote example uses curly punctuation. Use straight quotes and show curly quotes via escaped code points if needed.
Suggested change
-> He said “the project is on track” but others disagreed. +> He said \u201cthe project is on track\u201d but others disagreed.As per coding guidelines: "Use straight quotation marks ('"') instead of curly quotation marks ('"') in technical content and code documentation."
README.md-160-162 (1)
160-162:⚠️ Potential issue | 🟡 MinorAdd a trailing newline at EOF.
MD047 indicates the file lacks a single trailing newline.
README.md-126-128 (1)
126-128:⚠️ Potential issue | 🟡 MinorRemove emojis from the example bullets.
The examples should be emoji-free to match the formatting rules.
Proposed fix
-- 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers. -- 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards. -- ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends. +- **Speed:** Code generation is significantly faster, reducing friction and empowering developers. +- **Quality:** Output quality has been enhanced through improved training, contributing to higher standards. +- **Adoption:** Usage continues to grow, reflecting broader industry trends.As per coding guidelines: "Remove emojis from headings, bullet points, and content. Use plain text instead of decorative emoji."
adapters/vscode/HUMANIZER.md-463-489 (1)
463-489:⚠️ Potential issue | 🟡 MinorInsert blank lines around headings and reduce boldface.
MD022 indicates missing blank lines. Also, the bolded “Pattern X” labels are over-emphasized.
Proposed fix
-### Critical (immediate AI detection) +### Critical (immediate AI detection) + These patterns alone can identify AI-generated text: -- **Pattern 20:** Collaborative communication artifacts ("I hope this helps!", "Let me know if...") +- Pattern 20: Collaborative communication artifacts ("I hope this helps!", "Let me know if...")As per coding guidelines: "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
README.md-67-113 (1)
67-113:⚠️ Potential issue | 🟡 MinorReduce boldface usage in the pattern tables.
Every pattern name is bolded, which reads like mechanical emphasis. Use plain text and reserve bold for truly exceptional emphasis.
Proposed fix
-| 1 | **Significance inflation** | "marking a pivotal moment in the evolution of..." | "was established in 1989 to collect regional statistics" | +| 1 | Significance inflation | "marking a pivotal moment in the evolution of..." | "was established in 1989 to collect regional statistics" |As per coding guidelines: "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
adapters/antigravity-skill/SKILL_PROFESSIONAL.md-460-486 (1)
460-486:⚠️ Potential issue | 🟡 MinorAdd blank lines around headings and tone down bolding.
MD022 flags missing blank lines. Also, every bullet is bolded, which is over-emphasis.
Proposed fix
-### Critical (immediate AI detection) +### Critical (immediate AI detection) + These patterns alone can identify AI-generated text: -- **Pattern 20:** Collaborative communication artifacts ("I hope this helps!", "Let me know if...") +- Pattern 20: Collaborative communication artifacts ("I hope this helps!", "Let me know if...")As per coding guidelines: "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
adapters/copilot/COPILOT.md-463-489 (1)
463-489:⚠️ Potential issue | 🟡 MinorAdd blank lines around headings and reduce boldface.
The severity section triggers MD022 for missing blank lines. Also, bolding every “Pattern X” reads as mechanical emphasis.
Proposed fix
-### Critical (immediate AI detection) +### Critical (immediate AI detection) + These patterns alone can identify AI-generated text: -- **Pattern 20:** Collaborative communication artifacts ("I hope this helps!", "Let me know if...") +- Pattern 20: Collaborative communication artifacts ("I hope this helps!", "Let me know if...")As per coding guidelines: "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
adapters/gemini-extension/GEMINI.md-463-489 (1)
463-489:⚠️ Potential issue | 🟡 MinorAdd blank lines around headings and reduce bold emphasis in the severity list.
MD022 flags missing blank lines around headings. Also, the list uses bold on every item; the guideline calls for sparing bold usage.
Proposed fix
-### Critical (immediate AI detection) +### Critical (immediate AI detection) + These patterns alone can identify AI-generated text: -- **Pattern 20:** Collaborative communication artifacts ("I hope this helps!", "Let me know if...") +- Pattern 20: Collaborative communication artifacts ("I hope this helps!", "Let me know if...") -### High (strong AI indicators) +### High (strong AI indicators) + Multiple occurrences strongly suggest AI: -- **Pattern 1:** Significance inflation ("testament", "pivotal moment", "evolving landscape") +- Pattern 1: Significance inflation ("testament", "pivotal moment", "evolving landscape") -### Medium (moderate signals) +### Medium (moderate signals) + Common in AI but also in some human writing: -- **Pattern 13:** Em dash overuse +- Pattern 13: Em dash overuse -### Low (subtle tells) +### Low (subtle tells) + Minor indicators, fix if other patterns present: -- **Pattern 18:** Curly quotation marks +- Pattern 18: Curly quotation marksAs per coding guidelines: "Remove overuse of boldface. Use bold sparingly for true emphasis, not for mechanical emphasis of technical terms or phrase decoration."
🧹 Nitpick comments (1)
.agent/skills/humanizer-pro/SKILL.md (1)
52-52: Em dash usage in documentation content.Line 52 uses an em dash:
"casual" or "formal"—it's **alive**. Per the repository's own Pattern#13, em dashes should be used sparingly. Consider replacing with a comma or semicolon for consistency with the skill's own guidance.This is a minor nit since the file is primarily instructional content.
| --- | ||
| adapter_metadata: | ||
| skill_name: humanizer-pro | ||
| skill_version: 2.2.0 | ||
| last_synced: 2026-02-02 | ||
| source_path: SKILL_PROFESSIONAL.md | ||
| adapter_id: antigravity-skill-pro | ||
| adapter_format: Antigravity skill | ||
| --- |
There was a problem hiding this comment.
Version and sync date are behind the rest of the PR.
This file has skill_version: 2.2.0 and last_synced: 2026-02-02, while every other adapter in this PR was bumped to 2.2.1 / 2026-02-06. The second YAML block (line 14) also says version: 2.2.0. This looks like an oversight during the coordinated version bump.
Proposed fix
adapter_metadata:
skill_name: humanizer-pro
- skill_version: 2.2.0
- last_synced: 2026-02-02
+ skill_version: 2.2.1
+ last_synced: 2026-02-06
source_path: SKILL_PROFESSIONAL.mdAnd on line 14:
-version: 2.2.0
+version: 2.2.1🤖 Prompt for AI Agents
In @.agent/skills/humanizer-pro/SKILL.md around lines 1 - 9, Update the outdated
version metadata in the frontmatter and the second YAML block: change
adapter_metadata.skill_version from 2.2.0 to 2.2.1, update
adapter_metadata.last_synced from 2026-02-02 to 2026-02-06, and also change the
second block's version value (the YAML key named "version" on line 14) from
2.2.0 to 2.2.1 so both places match the PR's coordinated bump.
1 participant
User description
Summary
This PR migrates the repository's agent documentation from the proprietary WARP.md format to the open Agents.md standard.
Changes
Migrated to improve interoperability with tools like Cursor, Windsurf, and Claude Code.
PR Type
Enhancement, Documentation
Description
Migrated WARP.md to Agents.md standard for multi-agent interoperability
Added Pattern docs: migrate WARP.md to Agents.md standard blader/humanizer#19 (Primary Single Quotes) and bumped version to 2.2.0
Fixed grammatical errors (comma splices, missing commas, quote styles)
Updated sync scripts to propagate metadata to AGENTS.md and VS Code adapter
Consolidated repository context and guidelines into AGENTS.md manifest
Diagram Walkthrough
File Walkthrough
10 files
Comprehensive Agents.md manifest with repository contextUpdated pattern count to 25, added version history entryDeleted proprietary format fileAdded new track for adopting upstream PRsCreated track index for upstream PR adoptionDetailed plan for adopting three upstream PRsSpecification for upstream PR adoption workflowCreated track index for WARP to Agents.md migrationMigration plan with phases and verification stepsSpecification for WARP to Agents.md migration3 files
Added Pattern #19, fixed grammar, bumped to v2.2.0Added sync for AGENTS.md and VS Code HUMANIZER.mdSynced Pattern #19, grammar fixes, version 2.2.07 files
Updated skill_version metadata to 2.2.0Updated skill_version metadata to 2.2.0Updated skill_version metadata to 2.2.0Updated skill_version metadata to 2.2.0Updated skill_version metadata to 2.2.0Track metadata for upstream PR adoptionTrack metadata for WARP migration1 files
Added blank line for formatting consistency6 files
Added GitHub issues data fileAdded PR #3 metadata (YAML description fix)Added PR #4 diff (grammatical error fixes)Added PR #4 metadata (grammar fixes)Added PR #5 diff (Pattern #19 addition)Added PR #5 metadata (new pattern)Summary by CodeRabbit
New Features
Improvements
Documentation