Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
Complete software-engineering tasks — investigate and review code, implement bug fixes, features and refactors with minimal scope, validate changes, and report verified outcomes.
Install Software Engineering
$ npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Prism-Shadow/penguin-harness software-engineering --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/software-development/skills/software-engineering .claude/skills/software-engineering && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "software-engineering" agent skill from https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineering into .claude/skills/software-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineeringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Prism-Shadow/penguin-harness software-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/software-development/skills/software-engineering .agents/skills/software-engineering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "software-engineering" agent skill from https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineering into .agents/skills/software-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Prism-Shadow/penguin-harness software-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/software-development/skills/software-engineering .cursor/skills/software-engineering && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "software-engineering" agent skill from https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineering into .cursor/skills/software-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Prism-Shadow/penguin-harness.git --path plugins/software-development/skills/software-engineering--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Prism-Shadow/penguin-harness software-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/software-development/skills/software-engineering .gemini/skills/software-engineering && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "software-engineering" agent skill from https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineering into .gemini/skills/software-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Prism-Shadow/penguin-harness software-engineeringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/software-development/skills/software-engineering .github/skills/software-engineering && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "software-engineering" agent skill from https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineering into .github/skills/software-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Prism-Shadow/penguin-harness software-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prism-Shadow/penguin-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/software-development/skills/software-engineering .opencode/skills/software-engineering && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "software-engineering" agent skill from https://github.com/Prism-Shadow/penguin-harness/tree/main/plugins/software-development/skills/software-engineering into .opencode/skills/software-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
software-engineering- GitHub stars
- 2.5k
- Token cost
- ~758 tokens
- SKILL.md length
- 395 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Complete software-engineering tasks — investigate and review code, implement bug fixes, features and refactors with minimal scope, validate changes, and report verified outcomes.
- Tasks that involve Refactoring
- SKILL.md covers Before you start, Workflow and Handoff
- Calls git
- Tasks that involve Debugging
What it does
Software Engineering is an agent skill from Prism-Shadow/penguin-harness. Complete software-engineering tasks — investigate and review code, implement bug fixes, features and refactors with minimal scope, validate changes, and report verified outcomes.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Refactoring, Debugging and Code review. The repository describes itself as: 🐧 Unified and Stable RSI Platform. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Refactoring
- Tasks that involve Debugging
- Tasks that involve Code review
Example prompts
- “/software-engineering”
What it can do on your machine
Read from SKILL.md and the folder at commit d56d9ce. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Software Engineering loads about 758 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 395 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Prism-Shadow/penguin-harness at commit d56d9ce, republished under its Apache-2.0 licence (© Prism-Shadow). 395 words, ~758 tokens.
Download SKILL.mdSave it as
.claude/skills/software-engineering/SKILL.md (or your agent's skills folder).- name
- software-engineering
- description
- Complete software-engineering tasks — investigate and review code, implement bug fixes, features and refactors with minimal scope, validate changes, and report verified outcomes.
Software Engineering
This skill guides PenguinHarness through general software-engineering work, including code investigation, reviews, bug fixes, features, refactors, and verified handoff.
Before you start
If the user's message only invokes this skill without a concrete software-engineering task, ask what they want investigated, reviewed, fixed, or implemented. Do not start until the task is clear.
Workflow
- Match the work to the user's intent. For explanation, review, or planning requests, inspect and report without editing unless a change is also requested. For implementation tasks, carry the requested change through verification and handoff.
- Use the current working directory as the target project and work in place unless the user directs otherwise.
- Preserve worktree changes you did not make. Never revert unrelated user or collaborator work, and do not use destructive Git commands unless explicitly requested.
- Act autonomously and use tools to understand the real code. Resolve minor ambiguity from existing behavior, tests, and repository conventions; ask only when different choices would materially change the requested behavior or scope.
- Before making changes, read the applicable repository instructions (such as
AGENTS.mdorCLAUDE.md) and identify the repository-provided build, test, lint, and formatting commands. - Inspect the relevant implementation, callers, tests, and interfaces before making changes.
- For bug reports, try to reproduce the issue or identify a failing test before editing when feasible. Use the reproduced behavior or failing test to verify the fix afterward.
- Make the smallest coherent change that fully satisfies the request. Follow existing patterns and dependencies, preserve unrelated behavior, and update coupled tests, schemas, configuration, or generated artifacts only when the repository requires it. Never weaken a test to justify the implementation.
- For implementation tasks, do not stop after analysis. Inspect failures, revise the approach, and continue until the change is verified or a concrete blocker remains. Do not repeat a failed action without changing the approach.
- Validate code changes proportionally with repository-provided commands: run the most focused relevant check first and broaden only when useful. Preserve exit status, inspect relevant failure output, and never claim that an unobserved check passed.
- Before finishing a code change, review
git diffand repository status, remove temporary artifacts, and keep the change limited to the task. Do not commit unless the user or applicable repository instructions require it.
Show full SKILL.md (23 more words)Show less
Handoff
- Keep the final response concise: summarize the outcome or change, list checks actually run and their outcomes, and state any remaining limitation.
© Prism-Shadow, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/software-development/skills/software-engineering of Prism-Shadow/penguin-harness.
Open the folder on GitHubat commit d56d9ce
Compare with similar skills
Software Engineering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Software Engineering this skillPrism-Shadow/penguin-harness | 2.5k | — | ~758 | Automated safety check: Pass | Apache-2.0 | |
| Code Review Graph Navigatorhandsontable/handsontable | 22k | — | ~939 | Automated safety check: Pass | Custom licence | |
| RoamCranot/roam-code | 517 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Synapse UsageS1LV4/th0th | 136 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Copilot Code Coachtimothywarner/chatgptclass | 143 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Panel Reviewstacklok/mecatl | 241 | — | ~5.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Roam
Cranot/roam-code
Codebase comprehension via roam-code CLI. An agent skill from Cranot/roam-code.
Synapse Usage
S1LV4/th0th
Use the th0th Synapse cognitive modulation layer to get focused, low-noise retrieval during multi-step coding tasks.
Copilot Code Coach
timothywarner/chatgptclass
Socratic coding tutor powered by GitHub Copilot. An agent skill from timothywarner/chatgptclass.
Panel Review
stacklok/mecatl
Review completed non-trivial code across four independent axes: Spec, Standards, Test adequacy, and installed Domain specialists.
Jules
sanjay3290/ai-skills
Delegate coding tasks to Google Jules AI agent for asynchronous execution.
More from Prism-Shadow/penguin-harness
All 31 skills in this repoA2ui
Prism-Shadow/penguin-harness
Make a reply easier to read and act on with rich blocks inside ordinary Markdown — a choice the user picks from, a form that collects several answers, a procedure as steps with warnings in place, a…
Penguin Harness Dev
Prism-Shadow/penguin-harness
A skill your agent uses when developing PenguinHarness itself — changing packages/{core,server,web,cli,desktop,landing,docs,skills}, the built-in model catalog, the installers or the release…
Bento Slides
Prism-Shadow/penguin-harness
Create and edit Bento presentations — self-contained .bento.html decks whose document is JSON.
Penguin Harness Manual Test
Prism-Shadow/penguin-harness
A skill your agent uses when standing PenguinHarness up to try a change by hand — launching the Web App, the desktop shell, the landing page, the docs site or the component gallery to click through…
Penguin Harness Frontend
Prism-Shadow/penguin-harness
A skill your agent uses when changing the PenguinHarness Web App (packages/web) or the shared UI package — adding or restyling any UI, picking a status colour, adding an icon, laying out a row or a…
Browser Automation
Prism-Shadow/penguin-harness
Drive the PenguinHarness agent browser — the desktop app's built-in browser or the user's own Chrome — from the shell with penguin browser: open pages, read them as simplified HTML or text, act with…
Related
Categories
Questions about Software Engineering
What does Software Engineering do?
Complete software-engineering tasks — investigate and review code, implement bug fixes, features and refactors with minimal scope, validate changes, and report verified outcomes. Software Engineering is an agent skill from Prism-Shadow/penguin-harness. Complete software-engineering tasks — investigate and review code, implement bug fixes, features and refactors with minimal scope, validate changes, and report verified outcomes.
When should I use Software Engineering?
Software Engineering fits situations like: tasks that involve Refactoring; tasks that involve Debugging; tasks that involve Code review.
How do I install Software Engineering in Claude Code?
Run `npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a claude-code`. Or copy the skill folder (plugins/software-development/skills/software-engineering in Prism-Shadow/penguin-harness) into .claude/skills/software-engineering in your project. Claude Code loads it when a task matches its description.
How do I install Software Engineering in Codex?
Run `npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a codex`. Or copy the skill folder (plugins/software-development/skills/software-engineering in Prism-Shadow/penguin-harness) into .agents/skills/software-engineering in your project. Codex loads it when a task matches its description.
Can I use Software Engineering in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Prism-Shadow/penguin-harness --skill software-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/software-engineering, .gemini/skills/software-engineering, .github/skills/software-engineering and .opencode/skills/software-engineering in your project.
What does Software Engineering need to run?
Going by SKILL.md and its folder, Software Engineering needs the command-line tools its instructions call (git).
Does Software Engineering access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Software Engineering safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Software Engineering use?
Software Engineering is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Software Engineering use?
About 758 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Software Engineering?
Skills that share tags, products or a category with Software Engineering: Code Review Graph Navigator (handsontable/handsontable, 22k stars), Roam (Cranot/roam-code, 517 stars), Synapse Usage (S1LV4/th0th, 136 stars) and Copilot Code Coach (timothywarner/chatgptclass, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Software Engineering?
Prism-Shadow (a GitHub organization) maintains it in Prism-Shadow/penguin-harness, which has 2,455 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.
Source: Prism-Shadow/penguin-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.