terrylica/cc-skills

ignore

Manage global ignore patterns for lint-relative-paths.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/terrylica/cc-skills --skill ignore

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Navigation: Plugin CLAUDE.md | Root CLAUDE.md

Global Ignore Patterns

Manage global ignore patterns for the lint-relative-paths linter.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

Purpose

Some repositories intentionally use relative paths in markdown (e.g., ../docs/file.md) instead of repo-root paths (e.g., /docs/file.md). This command manages a global ignore file that skips path validation for matching workspaces.

Actions

ActionDescriptionExample
addAdd a pattern to the global ignore file/statusline-tools:ignore add my-repo
listShow current patterns/statusline-tools:ignore list
removeRemove a pattern from the ignore file/statusline-tools:ignore remove my-repo

Pattern Matching

Patterns use substring matching. A pattern matches if the workspace path contains the pattern.

Example: Pattern my-project matches:

  • /Users/user/projects/research-repo
  • /Users/user/eon/research-repo.worktree-feature-x
  • /home/user/code/research-repo-v2

Ignore File Location

~/.claude/lint-relative-paths-ignore

Lines starting with # are comments.

Execution

Skip Logic

  • If action + pattern provided -> execute directly
  • If only list provided -> show patterns immediately
  • If no arguments -> use AskUserQuestion flow

Workflow

  1. Check Current State: Run list to show existing patterns
  2. Action Selection: Use AskUserQuestion to select action:
  • "Add a new pattern" -> prompt for pattern
  • "Remove an existing pattern" -> show current patterns to select
  • "Just view current patterns" -> display and exit
  1. Pattern Input: For add/remove, AskUserQuestion with examples
  2. Execute: Run the management script
  3. Verify: Confirm changes applied

AskUserQuestion Flow (No Arguments)

When invoked without arguments, guide the user interactively:

Question: "What would you like to do with lint-relative-paths ignore patterns?"
Options:
  - "Add pattern" -> "Add a new repository pattern to skip path linting"
  - "List patterns" -> "Show all current ignore patterns"
  - "Remove pattern" -> "Remove an existing pattern from the ignore list"

For "Add pattern":

Question: "Enter the repository pattern to ignore"
Note: Patterns use substring matching. Example: 'research-repo' matches any path containing 'research-repo'.

Direct Execution (With Arguments)

Parse $ARGUMENTS and run the management script:

bash
/usr/bin/env bash << 'IGNORE_SCRIPT_EOF'
PLUGIN_DIR="$(cc-plugin-root statusline-tools)"
bash "$PLUGIN_DIR/scripts/manage-ignore.sh" $ARGUMENTS
IGNORE_SCRIPT_EOF

Manual Editing

The ignore file can also be edited manually:

bash
# View current patterns
cat ~/.claude/lint-relative-paths-ignore

# Add a pattern manually
echo "my-repo-pattern" >> ~/.claude/lint-relative-paths-ignore

Troubleshooting

IssueCauseSolution
Pattern not matchingSubstring match is strictUse broader pattern (e.g., forge vs research-repo)
Ignore file not found~/.claude doesn't existCreate with mkdir -p ~/.claude
Permission deniedFile not writableCheck file permissions with ls -la
Script not foundPlugin not installedReinstall plugin from marketplace

Post-Execution Reflection

After this skill completes, check before closing:

  1. Did the command succeed? — If not, fix the instruction or error table that caused the failure.
  2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
  3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

from this repository

More skills

All skills
terrylica
Community

academic-pdf-to-gfm

Convert academic PDF papers to GitHub-renderable GFM markdown with math equations. TRIGGERS - PDF, GitHub markdown, math

1h installs
1
GitHub stars
2
Updated
Nov 5
terrylica
Community

adr-code-traceability

Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.

1h installs
1
GitHub stars
2
Updated
Nov 5
terrylica
Community

arxiv-source-first-paper-ingest

Read an arXiv paper faithfully by fetching the authors' own LaTeX source instead of OCR-ing the PDF. Extracts every display equation with its label, environment and enclosing proposition, renders each to MathML, and proves usability by compiling each formula with a real TeX engine. Use when you need a paper's formulas exactly — to replicate a method, implement a loss function or custom objective, verify a quoted number, or check a claim against what the authors actually wrote. TRIGGERS - read th

1h installs
1
GitHub stars
2
Updated
Nov 5
terrylica
Community

azure-provision

Bootstrap Azure automation when interactive az login is blocked by a Conditional Access policy (error 530035, "Device state: Unregistered"). Mints a service principal through the Azure Portal session ONCE — using Microsoft Graph over a captured token, not DOM clicking — then provisions resource groups, Cognitive Services / AI Language / Speech resources and their keys entirely via az/REST, writing key AND endpoint together into the SCS vault. Use when az login fails but the portal works, when mo

1h installs
1
GitHub stars
2
Updated
Nov 5