Skip to content

Add /guide:introspect skill for Introspective Development#49

Merged
OriNachum merged 2 commits into
mainfrom
feature/introspect-skill
Apr 11, 2026
Merged

Add /guide:introspect skill for Introspective Development#49
OriNachum merged 2 commits into
mainfrom
feature/introspect-skill

Conversation

@OriNachum

Copy link
Copy Markdown
Owner

Summary

  • New /guide:introspect skill implementing the Introspective Development paradigm — audits lifecycle coverage, finds gaps in tooling and docs, and auto-fixes approved changes
  • New expert-tier reference doc explaining the 4 dimensions of Introspective Development
  • New introspection game-mode category (Expert tier, x100 multiplier) — tracked via /guide:introspect slash command
  • Three trigger levels (off/remind/auto) with natural language toggle and config persistence across plugin updates
  • Created issues Introspect: Agent-dispatched deep analysis (Approach C) #47 (agent-dispatched deep analysis) and Introspect: History tracking for persistent findings #48 (history tracking) for future enhancements

Closes #40

Files changed (14)

File Change
skills/introspect/SKILL.md New — the introspect skill
skills/ask/references/expert/introspective-development.md New — reference doc
hooks/scripts/track-prompt.sh guide:introspect → introspection (before guide:* catch-all)
hooks/scripts/track-stop.sh Multiplier, candidates, hint, count 15→16
hooks/scripts/migrate-data.sh Add introspection to EXPECTED
skills/game-mode/SKILL.md Schema, tier table, dashboard, count 15→16
skills/level-up/SKILL.md Dependency graph, roadmaps, hint
tests/helpers/setup.sh Add introspection to template
tests/track-prompt.bats 2 new tests for /guide:introspect tracking
tests/track-stop.bats Update suggestedFeatures
tests/migrate-data.bats Update counts 15→16
.claude-plugin/plugin.json Version 2.17.0
.claude-plugin/marketplace.json Version 2.17.0
CLAUDE.md Update structure tree + skills list

Test plan

  • All 98 bats tests pass (including 2 new introspect tracking tests)
  • Markdownlint clean (global config)
  • Manual: invoke /guide:introspect on a project — should produce meaningful report
  • Manual: invoke /guide:introspect auto — should update frontmatter and ask about PR skill

🤖 Generated with Claude Code

  • Claude

New skill that audits lifecycle coverage, finds gaps in tooling and docs,
and auto-fixes what it finds. Supports three trigger levels (off/remind/auto)
with natural language toggle and config persistence across plugin updates.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 11, 2026 21:37
@qodo-code-review

Copy link
Copy Markdown

Review Summary by Qodo

Add /guide:introspect skill for Introspective Development

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Add /guide:introspect skill implementing Introspective Development paradigm
• Audit lifecycle coverage, find gaps in tooling/docs, auto-fix approved changes
• New expert-tier game-mode category (x100 multiplier) with three trigger levels
• Integrate introspection tracking into game-mode scoring and feature suggestions
Diagram
flowchart LR
  A["User runs /guide:introspect"] --> B["Scan project state"]
  B --> C["Analyze four dimensions"]
  C --> D["Check lifecycle coverage"]
  D --> E["Report findings in plan mode"]
  E --> F["Apply approved fixes"]
  F --> G["Update CLAUDE.md/AGENT.md/skills"]
  H["Trigger level config"] --> I["auto/remind/off setting"]
  I --> J["Persists across plugin updates"]
  K["Game-mode integration"] --> L["Track introspection usage"]
  L --> M["Expert tier x100 multiplier"]
Loading

Grey Divider

File Changes

1. skills/introspect/SKILL.md ✨ Enhancement +225/-0

New introspect skill implementing Introspective Development

skills/introspect/SKILL.md


2. skills/ask/references/expert/introspective-development.md 📝 Documentation +132/-0

New expert reference doc on Introspective Development

skills/ask/references/expert/introspective-development.md


3. hooks/scripts/track-prompt.sh ✨ Enhancement +2/-0

Route /guide:introspect to introspection category

hooks/scripts/track-prompt.sh


View more (11)
4. hooks/scripts/track-stop.sh ✨ Enhancement +5/-4

Add introspection to expert tier and feature suggestions

hooks/scripts/track-stop.sh


5. hooks/scripts/migrate-data.sh ✨ Enhancement +1/-1

Add introspection to expected feature categories

hooks/scripts/migrate-data.sh


6. skills/game-mode/SKILL.md ✨ Enhancement +6/-4

Update game-mode schema and tier table for introspection

skills/game-mode/SKILL.md


7. skills/level-up/SKILL.md ✨ Enhancement +4/-0

Add introspection to dependency graph and roadmaps

skills/level-up/SKILL.md


8. tests/helpers/setup.sh 🧪 Tests +2/-1

Add introspection to game-data template

tests/helpers/setup.sh


9. tests/track-prompt.bats 🧪 Tests +11/-1

Add two new tests for /guide:introspect tracking

tests/track-prompt.bats


10. tests/track-stop.bats 🧪 Tests +1/-1

Update feature count and suggested features list

tests/track-stop.bats


11. tests/migrate-data.bats 🧪 Tests +4/-4

Update migration tests for 16 feature categories

tests/migrate-data.bats


12. .claude-plugin/plugin.json ⚙️ Configuration changes +1/-1

Bump version to 2.17.0

.claude-plugin/plugin.json


13. .claude-plugin/marketplace.json ⚙️ Configuration changes +1/-1

Bump version to 2.17.0

.claude-plugin/marketplace.json


14. CLAUDE.md 📝 Documentation +5/-1

Update structure tree and skills list documentation

CLAUDE.md


Grey Divider

Qodo Logo

@qodo-code-review

qodo-code-review Bot commented Apr 11, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0)   📘 Rule violations (2)   📎 Requirement gaps (2)   🎨 UX Issues (0)
📘\ ⚙ Maintainability (2)
📎\ ≡ Correctness (2)

Grey Divider


Action required

1. Expert level badge malformed 📘
Description
The new expert reference doc does not include the required level badge line immediately after the
# title in the exact format. This breaks the standardized reference-doc header convention and can
impact tooling or readers that rely on consistent structure.
Code

skills/ask/references/expert/introspective-development.md[R8-12]

+# Introspective Development
+
+> **Level: 🌳 Expert** | **Source:** [Claude Code Guide Plugin](https://github.com/OriNachum/claude-code-guide)
+
+[← Back to Automating Your Workflows](../intermediate/automating-your-workflows.md)
Evidence
PR Compliance ID 56378 requires the line immediately following the first # title in expert
reference docs to be exactly > **Level: 🌳**. In the added file, the line after `# Introspective
Development is blank and the next line includes additional text (Expert and Source:`), so the
badge is not in the required format or position.

Rule 56378: Enforce level badge after titles in ask skill reference docs
skills/ask/references/expert/introspective-development.md[8-12]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`skills/ask/references/expert/introspective-development.md` is missing the required expert badge line (`> **Level: 🌳**`) immediately after the `#` title, and the current badge line includes extra text.

## Issue Context
Per compliance, expert ask reference docs must have a standardized badge line directly after the first ATX title heading, with no extra content on that line.

## Fix Focus Areas
- skills/ask/references/expert/introspective-development.md[8-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Extra automation mechanisms listed 📘
Description
The new reference doc enumerates additional “mechanisms” beyond Hooks, Skills, and Sub Agents (e.g.,
MCP servers, CLAUDE.md updates, Scripts). This violates the requirement to restrict the
presented automation mechanisms to exactly three.
Code

skills/ask/references/expert/introspective-development.md[R53-60]

+Working with agents reveals friction — tasks that take more effort than they should, patterns that repeat without automation, context that gets lost between sessions. Act on these observations:
+
+- **Skills** — encode repeated workflows as slash commands
+- **Hooks** — automate event-driven actions (post-tool, pre-commit, session-end)
+- **MCP servers or agent skills** — wire external integrations for tools the agent needs
+- **Sub-agents** — create specialists for tasks that benefit from dedicated context
+- **CLAUDE.md updates** — capture hard-won project knowledge so future sessions start better
+- **Scripts** — reduce cognitive complexity of common tasks
Evidence
PR Compliance ID 56375 requires that only Hooks, Skills, and Sub Agents are presented as
automation mechanisms. In the new bullet list, additional items are presented as parallel ways to
act on friction (MCP servers or agent skills, CLAUDE.md updates, Scripts), effectively
introducing more than the allowed three.

Rule 56375: Restrict automation mechanisms to Hooks, Skills, and Sub Agents
skills/ask/references/expert/introspective-development.md[53-60]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The doc lists multiple parallel items for encoding/automation beyond the allowed set of three automation mechanisms.

## Issue Context
Compliance requires that when enumerating automation mechanisms, the list must be exactly: Hooks, Skills, Sub Agents (no fourth category).

## Fix Focus Areas
- skills/ask/references/expert/introspective-development.md[53-60]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


3. /guide:introspect lacks deep mode 📎
Description
The new /guide:introspect skill does not define any option/mode to dispatch four dimension-focused
sub-agents (Doc Loop, Lifecycle, Environment, Review) and merge their reports. This fails the
required “agent-dispatched deep analysis” capability.
Code

skills/introspect/SKILL.md[R22-73]

+### `help`
+
+Present available usage:
+
+| Usage | What it does |
+|---|---|
+| `/guide:introspect` | Introspect your project — infers focus from context |
+| `/guide:introspect [focus text]` | Introspect with a specific focus area |
+| `/guide:introspect auto` | Enable automatic introspection after PR merge |
+| `/guide:introspect remind` | Enable post-PR reminders to introspect |
+| `/guide:introspect off` | Disable automatic introspection |
+| `/guide:introspect help` | Show this help |
+
+Then stop.
+
+### Trigger level toggle
+
+If `$ARGUMENTS` matches any of these patterns, handle the toggle instead of scanning:
+
+**Detecting intent:**
+
+| Pattern | Level |
+|---|---|
+| `auto`, `call it automatically`, `run introspect after PRs`, `enable auto`, `automatically` | `auto` |
+| `remind`, `remind me`, `ask me after PRs`, `semi-auto` | `remind` |
+| `off`, `stop calling`, `don't run it automatically`, `disable`, `manual only` | `off` |
+
+If the intent is unclear, ask the user which level they want.
+
+**Applying the toggle:**
+
+1. Read `${CLAUDE_PLUGIN_ROOT}/.local/game-data.json` (create the `introspectConfig` key if missing)
+2. Set `introspectConfig.triggerLevel` to the chosen level (`auto`, `remind`, or `off`)
+3. Write the updated game-data.json
+
+4. If level is `auto`:
+   - Edit this file's frontmatter: set `disable-model-invocation: false`
+   - Search the project for a PR review skill: look in `.claude/skills/`, `skills/`, and installed plugins for any skill whose description mentions "PR", "pull request", or "review"
+   - If found: ask the user "Found **[skill name]**. Update it to call `/guide:introspect` after PR merge?"
+   - If not found: ask the user "No PR review skill found. Create one?" AND add to CLAUDE.md: "After merging a PR, run `/guide:introspect` to review what could be improved."
+   - Tell the user: "Restart Claude Code for automatic introspection to take effect."
+
+5. If level is `remind`:
+   - Keep this file's frontmatter as `disable-model-invocation: true`
+   - Same PR skill search as `auto`, but the instruction becomes: "After merging a PR, remind the user: 'Want to introspect? Run `/guide:introspect`'"
+   - Tell the user: "Restart Claude Code for the reminder to take effect."
+
+6. If level is `off`:
+   - Edit this file's frontmatter: set `disable-model-invocation: true`
+   - Tell the user: "Automatic introspection disabled. You can still run `/guide:introspect` manually anytime. Restart Claude Code for the change to take effect."
+
+Then stop.
Evidence
PR Compliance ID 322803 requires an explicit deep analysis mode that invokes four dimension-focused
agents and merges outputs. The skill’s documented argument handling and flows include help and
trigger toggles only, and describe a single-agent scan/analyze/report process with no deep/parallel
dispatch or merge step.

Support Approach C: agent-dispatched deep analysis for /guide:introspect across key dimensions
skills/introspect/SKILL.md[22-73]
skills/introspect/SKILL.md[84-163]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`/guide:introspect` lacks an optional mode to run deep, parallel introspection by dispatching four dimension-specific sub-agents and merging their outputs.

## Issue Context
Compliance requires Approach C: a deep-analysis option that invokes four agents (Doc Loop, Lifecycle, Environment, Review) and consolidates their reports.

## Fix Focus Areas
- skills/introspect/SKILL.md[22-73]
- skills/introspect/SKILL.md[84-163]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


View more (2)
4. /guide:introspect lacks history tracking 📎
Description
The new /guide:introspect skill does not persist findings across runs, cross-reference previous
findings, or provide a history viewing command. This prevents improvement-over-time summaries and
causes repeated reporting of already-resolved gaps.
Code

skills/introspect/SKILL.md[R22-56]

+### `help`
+
+Present available usage:
+
+| Usage | What it does |
+|---|---|
+| `/guide:introspect` | Introspect your project — infers focus from context |
+| `/guide:introspect [focus text]` | Introspect with a specific focus area |
+| `/guide:introspect auto` | Enable automatic introspection after PR merge |
+| `/guide:introspect remind` | Enable post-PR reminders to introspect |
+| `/guide:introspect off` | Disable automatic introspection |
+| `/guide:introspect help` | Show this help |
+
+Then stop.
+
+### Trigger level toggle
+
+If `$ARGUMENTS` matches any of these patterns, handle the toggle instead of scanning:
+
+**Detecting intent:**
+
+| Pattern | Level |
+|---|---|
+| `auto`, `call it automatically`, `run introspect after PRs`, `enable auto`, `automatically` | `auto` |
+| `remind`, `remind me`, `ask me after PRs`, `semi-auto` | `remind` |
+| `off`, `stop calling`, `don't run it automatically`, `disable`, `manual only` | `off` |
+
+If the intent is unclear, ask the user which level they want.
+
+**Applying the toggle:**
+
+1. Read `${CLAUDE_PLUGIN_ROOT}/.local/game-data.json` (create the `introspectConfig` key if missing)
+2. Set `introspectConfig.triggerLevel` to the chosen level (`auto`, `remind`, or `off`)
+3. Write the updated game-data.json
+
Evidence
PR Compliance ID 322804 requires persistent storage of findings with timestamps and an explicit
history view command. The skill only documents persisting introspectConfig.triggerLevel and its
help/commands do not include any history command or any storage schema for findings.

Persist /guide:introspect findings across runs with history viewing and cross-referencing
skills/introspect/SKILL.md[22-56]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`/guide:introspect` does not persist findings across runs (with timestamps), does not cross-reference prior findings, and has no `history` view command.

## Issue Context
Compliance requires storing findings (e.g., `.local/introspect-findings.json` or `game-data.json` under `introspectConfig.findings`), avoiding re-reporting resolved items, and exposing a history display command.

## Fix Focus Areas
- skills/introspect/SKILL.md[22-56]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


5. Config stored in game-data🐞
Description
/guide:introspect toggle flow persists introspectConfig inside .local/game-data.json, but that
file is not guaranteed to exist unless game mode created it and it is explicitly deleted by
/guide:game-mode reset. This makes the new trigger-level persistence unreliable (can fail on fresh
installs and can be wiped by a game-mode reset).
Code

skills/introspect/SKILL.md[R53-56]

+1. Read `${CLAUDE_PLUGIN_ROOT}/.local/game-data.json` (create the `introspectConfig` key if missing)
+2. Set `introspectConfig.triggerLevel` to the chosen level (`auto`, `remind`, or `off`)
+3. Write the updated game-data.json
+
Evidence
The new skill instructs reading/writing ${CLAUDE_PLUGIN_ROOT}/.local/game-data.json to store
introspectConfig.triggerLevel, but the runtime hook migration won’t create that file if it doesn’t
already exist (no cache), and game-mode reset deletes the file entirely—so the introspect config can
be missing or lost.

skills/introspect/SKILL.md[51-56]
hooks/scripts/migrate-data.sh[10-34]
hooks/scripts/track-prompt.sh[8-13]
skills/game-mode/SKILL.md[189-193]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`/guide:introspect` persists `introspectConfig.triggerLevel` in `.local/game-data.json`, which may not exist unless game mode was enabled and can be deleted by `/guide:game-mode reset`. This breaks the promise of persistent trigger configuration.

## Issue Context
- Hook scripts only migrate/operate on `game-data.json` if it already exists (or can be restored from cache).
- Game mode reset explicitly deletes `game-data.json`, which would wipe any introspection settings stored there.

## Fix Focus Areas
- skills/introspect/SKILL.md[51-83]

## Suggested fix approach
- Store introspection settings in a dedicated file, e.g. `${CLAUDE_PLUGIN_ROOT}/.local/introspect-config.json`.
 - On toggle: create `${CLAUDE_PLUGIN_ROOT}/.local/` if missing; create the config file with defaults if missing.
 - Read/write `triggerLevel` from that file instead of `game-data.json`.
- Update the “Config persistence check” section to read the dedicated config file.
- (Optional) If you intentionally want to colocate config with game-mode data, then explicitly add handling for missing `game-data.json` (create a minimal structure with `enabled:false`), and document that `/guide:game-mode reset` will also reset introspect settings.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Advisory comments

6. Misleading suggestedFeatures test🐞
Description
The track-stop test claims it pre-populates “all level 1-2 candidates” but includes introspection,
which is only a level 3+ candidate per the hook logic. This makes the test setup inconsistent with
the behavior it’s describing.
Code

tests/track-stop.bats[R211-213]

+  jq '.suggestedFeatures = ["btw","skills","plugins","web","planning","notebooks","mcp","loop","tasks","introspection"]' \
    "$DATA_FILE" > "${DATA_FILE}.tmp" && mv "${DATA_FILE}.tmp" "$DATA_FILE"
  output="$(run_hook '{"usage": {"input_tokens": 0, "output_tokens": 0}}')"
Evidence
track-stop.sh only includes introspection in the candidate set when LEVEL >= 3, but the test
comment says it’s pre-populating level 1-2 candidates while adding introspection to
suggestedFeatures.

hooks/scripts/track-stop.sh[117-122]
tests/track-stop.bats[208-213]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`tests/track-stop.bats` pre-populates `suggestedFeatures` with `introspection` while describing the list as “all level 1-2 candidates,” but `introspection` is only considered for level 3+.

## Issue Context
This is not a product bug, but it can confuse future maintainers and make the test intent unclear.

## Fix Focus Areas
- tests/track-stop.bats[208-213]

## Suggested fix approach
- Either remove `"introspection"` from the pre-populated array (so it matches the level 1-2 candidate list),
- Or update the comment to reflect what the list actually represents (e.g., “pre-populate with all candidates for this test”).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new /guide:introspect skill and supporting documentation + game-mode tracking so “Introspective Development” usage is counted as a new expert-tier feature category.

Changes:

  • Introduces the new skills/introspect/SKILL.md and an expert reference doc describing the Introspective Development paradigm.
  • Adds a new introspection expert-tier game-mode category (x100) and wires /guide:introspect prompt tracking to it.
  • Updates schema migration, level-up/game-mode docs, and bats tests to reflect the new 16th category and ensure tracking remains correct.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
skills/introspect/SKILL.md New introspection skill instructions, including trigger-level toggle behavior and introspection workflow.
skills/ask/references/expert/introspective-development.md New expert reference doc explaining the paradigm and how to use /guide:introspect.
hooks/scripts/track-prompt.sh Routes /guide:introspect to the new introspection feature category before the guide:* skip rule.
hooks/scripts/track-stop.sh Treats introspection as expert-tier (x100), includes it in suggestion candidates, and updates unlocked-count output to /16.
hooks/scripts/migrate-data.sh Adds introspection to the EXPECTED feature list for lightweight schema migration.
skills/game-mode/SKILL.md Updates the documented schema/tier table/dashboard examples for 16 categories including introspection.
skills/level-up/SKILL.md Adds introspection to the dependency graph, roadmap examples, and hint text.
tests/helpers/setup.sh Extends the test game-data.json template to include introspection.
tests/track-prompt.bats Adds coverage that /guide:introspect (with/without args) increments the introspection count.
tests/track-stop.bats Updates suggestedFeatures fixture to include introspection to match the expanded category set.
tests/migrate-data.bats Updates category count and expected-category loops from 15 → 16.
.claude-plugin/plugin.json Bumps plugin version to 2.17.0.
.claude-plugin/marketplace.json Bumps marketplace version to 2.17.0.
CLAUDE.md Updates repo structure tree + skill list to include /guide:introspect.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread tests/migrate-data.bats Outdated
Comment thread tests/track-stop.bats Outdated
Comment thread skills/ask/references/expert/introspective-development.md
Comment thread skills/ask/references/expert/introspective-development.md
Comment thread skills/introspect/SKILL.md
Comment thread skills/introspect/SKILL.md
Comment thread skills/introspect/SKILL.md Outdated
…sistence

- Update test comment "All 15" → "All 16" categories (Copilot)
- Remove expert-tier introspection from level 1-2 suggestedFeatures (Copilot)
- Handle missing game-data.json in toggle flow — create dir/file if needed (Qodo)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@OriNachum OriNachum merged commit 21808cc into main Apr 11, 2026
2 checks passed
@OriNachum OriNachum deleted the feature/introspect-skill branch April 11, 2026 21:57
OriNachum added a commit that referenced this pull request Apr 11, 2026
… skill

Fixes from running /guide:introspect on this repo after PR #49:
- Remove AGENT.md references from skill (Agentic Folders deferred)
- Add introspect skill to README.md and index.md
- Add markdownlint config to repo root for contributor consistency
- Add "Clear" phase guidance to CLAUDE.md Git Workflow section
- Fix ordered list numbering in SKILL.md

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
OriNachum added a commit that referenced this pull request Apr 11, 2026
* Apply introspection findings: update docs, add linting config, refine skill

Fixes from running /guide:introspect on this repo after PR #49:
- Remove AGENT.md references from skill (Agentic Folders deferred)
- Add introspect skill to README.md and index.md
- Add markdownlint config to repo root for contributor consistency
- Add "Clear" phase guidance to CLAUDE.md Git Workflow section
- Fix ordered list numbering in SKILL.md

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Fix review comments: version bump, Contributing count, Agentic Folders ref

- Bump version 2.17.0 → 2.17.1 (patch: content changes to shipped skill)
- Fix Contributing section: "five skills" → "seven skills", add introspect/
- Soften Agentic Folders reference in Origin section (future consideration)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add /guide:introspect skill to improve setup

2 participants