npx skills add smithery/janjaszczak --skill repo-grounding
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.
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.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installsConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…
566.3K installsAzure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…
510K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsAlso in this package
Other skills from janjaszczak/cursor · top by installs.
npx skills add 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.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Read FileSearch(*)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.md1,104 B -
docs
SUMMARY.md207 B
History
- First seen on skills.sh
- 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
- Identify likely files (paths mentioned, conventional locations).
- Read the minimum subset (start with entrypoints/config).
- Quote exact fragments when asserting repo facts.
- If a change is requested: propose plan with file list and exact edits.
Output
- Evidence-based: cite file paths + key excerpts + recommended edit plan.