Convert GitHub issues and TODO items into a prioritized Jekyll website task backlog.
npx skills add https://github.com/christophevg/c3 --skill website-manage
Please help me install this Agent Skill. Skill: website-manage Source: https://github.com/christophevg/c3/tree/main/skills/website-manage Command: npx skills add https://github.com/christophevg/c3 --skill website-manage
It solves the problem of organizing and executing website content changes without getting lost between GitHub issues, a backlog, and iterative page updates—especially for Jekyll/static sites.
_config.yml, working with typical site files like _posts/, _pages/, _data/, and _includes/.Use cases include: adding or fixing content, updating page structure, refining templates/includes, and turning issues/TODO ideas into implemented, review-approved changes.
Tell the AI: "Manage my website tasks for this Jekyll project and propose the next changes after syncing with GitHub issues."
High-intent search queries and answers about installing and using this skill.
You can manage Jekyll website content updates by syncing with a remote repository to pull open GitHub issues into a prioritized TODO backlog. The workflow requires a git pull first, then converts issues into iterative implementation steps for user review.
Yes, iterative static site page updates follow a plan-step-review-iterate loop that commits changes only after explicit user approval. This conversational workflow breaks website modifications into small reviewable steps to ensure controlled content deployment.
The best way to organize unsorted TODO items and GitHub issues for a static website is through interactive priority assignment. This creates a structured task backlog that guides iterative content and structure updates sequentially.
Yes, the website management workflow requires a _config.yml file to detect Jekyll projects. It specifically targets Jekyll site structures, working with conventional directories like _posts/, _pages/, _data/, and _includes/ for content updates.
To add or fix content on a Jekyll site, you initiate a conversational git workflow that proposes changes after syncing with GitHub issues. The process handles page structure refinements and template updates, requiring explicit approval before committing.
A key limitation of this iterative git workflow is that it requires explicit user approval before any commit is made, preventing fully automated deployment. Additionally, it exclusively targets static website projects where a _config.yml file is present.
cxnaiveReview local git changes and GitHub pull requests with automated feedback.
ovineyAutomate the end-to-end Jekyll development workflow for blog maintenance.
sweeden-ttuGenerate Jekyll site scaffolds with layouts, includes, and KaTeX, Mermaid, and Reveal.js assets.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.