Charlie Guse
Community@charlesguse
Charlie Guse maintains spec-driven development commands for GitHub spec-kit projects plus GitHub Actions YAML review skills for step-gating and container-shell defects.
Agent Skills by Charlie Guse
Showing 12 vetted skills indexed across 1 GitHub repositories.
charlesgusespeckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
charlesgusereview-step-gating
Detects GitHub Actions guards that strand teardown and degradation steps after tolerated failures.
charlesgusecontainer-shell-safety
Detects unpinned shell steps in caller-supplied-container GitHub Actions jobs.
charlesgusespeckit-constitution
Creates or updates the project constitution file from provided principles and template resolution.
charlesgusespeckit-implement
Executes implementation plans by processing all tasks defined in tasks.md.
charlesgusespeckit-converge
Assess codebase against spec, plan, and tasks, then append remaining work to tasks.md.
charlesgusespeckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.
charlesgusespeckit-clarify
Identifies underspecified areas in feature specs and encodes clarification answers back into the spec.
charlesgusespeckit-plan
Generates implementation plans and design artifacts from feature specifications using spec-kit templates.
charlesgusespeckit-analyze
Analyze spec.md, plan.md, and tasks.md for cross-artifact consistency and coverage gaps.
charlesgusespeckit-specify
Generate a validated feature specification from a natural language feature description.
charlesgusespeckit-tasks
Generates a dependency-ordered tasks.md checklist from spec-kit design artifacts.
Frequently Asked Questions About Charlie Guse
FAQPage SchemaWhat tasks can I perform with charlesguse's skills?▼
You can run the full spec-kit lifecycle: specify features, clarify underspecified areas, generate plans and tasks.md, analyze cross-artifact consistency, implement tasks, and convert tasks to GitHub issues. Two additional skills review GitHub Actions YAML for step-gating and container-shell defects.
Who should use these skills?▼
Software engineers and maintainers practicing spec-driven development with GitHub's spec-kit, plus reviewers hardening CI/CD pipeline changes. They suit developers editing .github/workflows files who need to catch always() misuse, stranded teardown paths, and non-bash shell exposure in container jobs.
What are the prerequisites and dependencies?▼
The ten speckit-* skills require an existing spec-kit project structure containing a .specify/ directory. The two GitHub Actions review skills read .github/workflows/*.yml files and require python3 with PyYAML installed to parse the pipeline definitions.
How do the GitHub Actions review skills work in practice?▼
Invoke review-step-gating or container-shell-safety when writing or reviewing any workflow change touching if:, continue-on-error:, container: blocks, or run: steps. The skill parses the YAML and flags guards that strand teardown paths, always() versus !cancelled() errors, and missing shell: bash declarations.
Are these skills open source and what do they cost?▼
The skills are published publicly in charlesguse's GitHub registry at no cost, with the speckit-* commands sourced from github-spec-kit templates (templates/commands/*.md). No paid license or subscription is indicated in the manifest; only the spec-kit project structure and PyYAML runtime are needed.