janjaszczak/cursor

repo-grounding

Ground answers in the repository by reading relevant files, configs, and code paths. Use when the user asks to modify/debug code, configuration, CI/CD, or wants repo-specific reasoning.

First seen Feb 21, 2026

Installation

$ npx skills add janjaszczak/cursor --skill repo-grounding

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from janjaszczak/cursor · top by installs.

npx skills add janjaszczak/cursor

Browse all from janjaszczak/cursor

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityRequires repo access in Cursor workspace and file search/read tools.
Allowed toolsRead FileSearch(*)
Declared agents cursor
More metadata
intent
Avoid repo scanning overhead for generic Q&A.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,104 B
  • docs SUMMARY.md 207 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

repo-grounding

Activation gate (anti-noise)

Run only if the user asks for:

  • Code change, refactor, fix, debug, performance work in THIS repo.
  • Analysis of existing config/scripts.
  • “Where is X implemented?” in this repo.

Skip if:

  • Pure conceptual question (no repo action).
  • The user wants a generic best-practice answer.

Procedure

  1. Identify likely files (paths mentioned, conventional locations).
  2. Read the minimum subset (start with entrypoints/config).
  3. Quote exact fragments when asserting repo facts.
  4. If a change is requested: propose plan with file list and exact edits.

Output

  • Evidence-based: cite file paths + key excerpts + recommended edit plan.