Add shellgAIde GNU-first Bash resources

[fragolinux]

This PR adds a new shellgAIde entry focused on strict, GNU-first Bash scripting (Bash >= 5) with Google Shell Style Guide structure and zero ShellCheck warnings.

Repository: https://github.com/fragolinux/shellgAIde

What's included

• A shellgAIde GNU-first Bash instruction file that defines the target environment, mandatory script structure (shebang + header markers + main()), and hard gates (ShellCheck + shfmt).
• A companion prompt that guides users to generate/refactor scripts following the instruction file.
• A companion agent definition aligned with the same constraints (catalog/reference).
• The skill remains unchanged (kept verbose on purpose).

Why the name
shellgAIde is a pun that sounds like “shellguide”:

• shell: the domain (bash, shell scripting)
• gAIde: a “guide” powered by AI, inspired by the Google Shell Style Guide (G = Google, AI = assistant, de = deterministic environment).

Validation

• npm run build
• npm run collection:validate
• npm run skill:validate
• bash scripts/fix-line-endings.sh

[Copilot]

Pull request overview

This PR introduces shellgAIde, a new collection of GitHub Copilot resources for GNU-first Bash >= 5 scripting with strict safety requirements, Google Shell Style Guide compliance, and zero ShellCheck warnings. The contribution includes a skill definition, instruction file, prompt template, and agent mode definition, all emphasizing deterministic, GNU-only tooling without cross-platform compatibility branches.

Key Changes:

• New skill for GNU-first Bash scripting with mandatory structure requirements (shebang, header markers, main() function)
• Instruction file defining strict safety baseline and lint gates (ShellCheck, shfmt)
• Companion prompt and agent definitions aligned with the same GNU-first constraints

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
skills/shellgaide-gnu-bash/SKILL.md	Defines the new shellgAIde skill with comprehensive GNU-first Bash scripting requirements
prompts/shellgaide-gnu-bash-script.prompt.md	Prompt template for generating/refactoring GNU-first Bash scripts
instructions/shellgaide-gnu-bash.instructions.md	Instruction file establishing GNU-first Bash coding standards for .sh/.bash files
agents/shellgaide-gnu-bash.agent.md	Agent mode definition for interactive GNU-first Bash script assistance
docs/README.skills.md	Adds shellgaide-gnu-bash entry to skills table
docs/README.prompts.md	Adds shellgAIde prompt entry to prompts table
docs/README.instructions.md	Adds shellgAIde instructions entry to instructions table
docs/README.agents.md	Adds shellgaide-gnu-bash agent entry to agents table

[fragolinux]

i fixed all issues and pushed again, please check again

[Copilot]

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated no new comments.

[fragolinux]

Hi maintainers — this PR is ready for review.\n\nIt adds shellgAIde GNU-first Bash resources (instructions + prompt + agent catalog entry + skill) and keeps generated docs in sync.\n\nAll checks are green. Thanks for taking a look.

[codemillmatt]

I wonder if this would be suited as a single skill w/ referenceable files & examples within it? (it may be possible I'm misunderstanding the overall intent here though).

[fragolinux]

I wonder if this would be suited as a single skill w/ referenceable files & examples within it? (it may be possible I'm misunderstanding the overall intent here though).

honestly, i'm trying to keep up with all the changes happening in copilot lately and to figure it out which is the best resource to use between prompts, agents, skills, mcp, and now spec kits (saw video introducing them just yesterday)...

i'd be glad if you would clarify your concerns or you have ideas to enhance this...

it started as a prompt to be used to produce well formed (as google bash guidelines) bash scripts, and a tool chain to check them in any way i could think... then found this repo and thought to share my work in it, and as said, trying to understand all of this and what it's best to be used...

opened to any suggestion, thank you!

the goal is to be able to create or refactor bash scripts which follow those guidelines and pass shellcheck/shfmt checks...

[codemillmatt]

honestly, i'm trying to keep up with all the changes happening in copilot lately and to figure it out which is the best resource to use between prompts, agents, skills, mcp, and now spec kits (saw video introducing them just yesterday)

Funny you should say this - we're currently working on a way to help folks keep up and learn best practices etc.

Anyway - a skill is going to let an agent (whether it's a custom one or not) the ability to perform specialized tasks. https://code.visualstudio.com/docs/copilot/customization/agent-skills

I don't have any concerns per se - just want this to fit in so it can help as many folks as possible. And if it makes sense for it to only be a skill - you don't have to worry about maintaining a bunch of things.

Take a look at this too: https://agentskills.io/home and let me know what you think. This feels like a skill to me. (And possibly a prompt file if you know people would probably want to use the same prompt over and over.)

[fragolinux]

I don't have any concerns per se - just want this to fit in so it can help as many folks as possible. And if it makes sense for it to only be a skill - you don't have to worry about maintaining a bunch of things.

Take a look at this too: https://agentskills.io/home and let me know what you think. This feels like a skill to me. (And possibly a prompt file if you know people would probably want to use the same prompt over and over.)

thank you, i'll check your links tomorrow, i'm ok in reducing complexity, always...