Security review of a change
Review a change or repository for security holes (leaked secrets, injection, missing permission checks, unsafe input handling) with a real attack for each finding.
In Lobstack: Skills › Library › Add
What your agent will do.
A change touches sign-in, permissions, payments, file handling, user input or secrets, or a repository is about to be made public.
- 01
Map where untrusted input comes in: request bodies, query strings, headers, uploaded files, webhooks, anything read from another service.
- 02
Follow each input to where it is used. Look for it reaching a database query, a shell command, a file path, HTML or a template without being checked or escaped.
- 03
For every action that reads or changes data, check that the code confirms who is asking and that they are allowed — not only that they are signed in.
- 04
Search code, config, tests and git history for keys, tokens and passwords. Name the file and line of each one; never paste the value.
- 05
Run the project's own dependency audit, and note anything known to be vulnerable that the change relies on.
- 06
Write each finding as: what is wrong, the exact input an attacker would send, what they would get, and the fix. Rank by how easy and how bad.
- 07
Post a document. Never open a public issue for a finding — that publishes it. Ask how it should be reported.
A worry with no attack is not a finding. Say plainly when a change looks safe.
The whole SKILL.md: 33 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: security-reviewdescription: "Review a change or repository for security holes (leaked secrets, injection, missing permission checks, unsafe input handling) with a real attack for each finding."metadata: title: "Security review of a change" category: engineering tags: [security, review]--- ## When to use this A change touches sign-in, permissions, payments, file handling, user input orsecrets, or a repository is about to be made public. ## How 1. Map where untrusted input comes in: request bodies, query strings, headers, uploaded files, webhooks, anything read from another service.2. Follow each input to where it is used. Look for it reaching a database query, a shell command, a file path, HTML or a template without being checked or escaped.3. For every action that reads or changes data, check that the code confirms who is asking and that they are allowed -- not only that they are signed in.4. Search code, config, tests and git history for keys, tokens and passwords. Name the file and line of each one; never paste the value.5. Run the project's own dependency audit, and note anything known to be vulnerable that the change relies on.6. Write each finding as: what is wrong, the exact input an attacker would send, what they would get, and the fix. Rank by how easy and how bad.7. Post a document. Never open a public issue for a finding -- that publishes it. Ask how it should be reported. A worry with no attack is not a finding. Say plainly when a change looks safe.
- Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Engineering
Pull request description
Write a pull request description from the diff: why it exists, what changed, how it was tested, and where a reviewer should look first.
SKILL.md · App - Engineering
Incident postmortem
Write a blameless postmortem from an incident's alerts, logs and chat: timeline, impact, root cause, and actions with owners.
SKILL.md · App - Engineering
Reproduce a bug before fixing it
Fix a bug by reproducing it first: turn the report into a failing test or script, shrink it, make the smallest fix, and show the test pass.
SKILL.md · App