One-click install
npx skills add https://github.com/Christos-Hadjinikolis/Christos-Hadjinikolis.github.io --skill site-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-maintenance
Source: https://github.com/Christos-Hadjinikolis/Christos-Hadjinikolis.github.io/tree/main/.codex/skills/site-maintenance
Command: npx skills add https://github.com/Christos-Hadjinikolis/Christos-Hadjinikolis.github.io --skill site-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you safely maintain and modify a Jekyll site’s structure and behavior without breaking templates, publishing private content, or introducing navigation and URL regressions.

Core Features & Use Cases

  • Repository change planning for Jekyll: Guides edits to _config.yml, _layouts/, _includes/, content/pages/, content/_posts/, and content/_sections/ with a clear before-you-change inspection workflow.
  • Guardrails against accidental publishing: Emphasizes treating _internal/ as non-published and avoiding front matter or permalink mistakes that could expose internal docs.
  • Operational validation via Make targets: Recommends using make build and make audit to catch issues related to generated output, URL discoverability, feeds, analytics, and 404 handling.

Quick Start

Use this skill to review and fix your proposed Jekyll change—such as updating a homepage section or correcting a template/navigation issue—before you run a local build and audit to confirm the rendered site behavior.

Frequently Asked Questions about site-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely edit Jekyll templates without breaking site navigation?

To safely edit Jekyll templates, inspect `_layouts/`, `_includes/`, and `_config.yml` before making changes. This prevents URL regressions and navigation breaks by enforcing structural guardrails and validating modifications through source inspection.

What is the best way to prevent accidental publishing of internal Jekyll docs?

Preventing accidental publishing of internal Jekyll docs requires treating the `_internal/` directory as non-published. You must avoid front matter or permalink mistakes that could accidentally expose private content to the public website.

How do I validate Jekyll configuration changes before publishing?

Validate Jekyll configuration changes by running Make targets like `make build` and `make audit`. These commands catch issues related to generated output, URL discoverability, feeds, analytics, and 404 handling before you publish.

Can I use this workflow to add new homepage sections to a Jekyll site?

Yes, you can use this workflow to add new homepage sections to a Jekyll site. The process guides edits to `content/_sections/` and `content/pages/` while preserving the existing Prologue structure and enforcing operational guardrails.

Why does my Jekyll site audit fail after a template modification?

A Jekyll site audit fails after template modification when changes introduce URL discoverability issues, feed errors, or 404 handling problems. Running `make audit` inspects generated output to catch these structural regressions.